Add more detailed assert option - #1153
Merged
Merged
Conversation
Member
|
What is the purpose of this change? |
Hypexion
changed the title
Collaborator
Author
Had a think about the goal, which is to allow for the possibility of more detailed asserts. This led me to do a completely different solution. |
mrimer
approved these changes
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new kind of assert,
ASSERT_DETAIL. This allows an extra piece of information (currently a raw string or unsigned int) to be spliced into an assert message for more detailed reporting.As a live example, I've changed several asserts in
DbPackedVarsto use this new assert type.