Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

assert: Report why values aren't equal #11043

Merged
merged 4 commits into from
Jul 22, 2024
Merged

assert: Report why values aren't equal #11043

merged 4 commits into from
Jul 22, 2024

Commits on Jul 5, 2024

  1. assert: Report why values aren't equal

    @roberth
    roberth committed Jul 5, 2024
    Configuration menu
    Copy the full SHA
    d63bd82 View commit details
    Browse the repository at this point in the history

Commits on Jul 10, 2024

  1. assertEqValues: clarify potential bug error message

    @roberth
    roberth committed Jul 10, 2024
    Configuration menu
    Copy the full SHA
    1352222 View commit details
    Browse the repository at this point in the history

Commits on Jul 11, 2024

  1. Add EvalErrorBuilder::panic() 

    An nicer alternative to printError + abort, or assert(false /* foo */)
    @roberth
    roberth committed Jul 11, 2024
    Configuration menu
    Copy the full SHA
    6157740 View commit details
    Browse the repository at this point in the history

  2. eqValues/assertEqValues: Clean up assertions 

    It's still paranoid, and probably a waste of words, but at least
now it's consistent and readily identifyable from a log.
    @roberth
    roberth committed Jul 11, 2024
    Configuration menu
    Copy the full SHA
    56bf39e View commit details
    Browse the repository at this point in the history