-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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.
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
lib/trivial: add assertMsg and assertMsgOneOf #44136
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
1e6af87
lib/trivial: add assertMsg
Profpatsch 0f178f6
lib/trivial: add assertOneOf
Profpatsch 5582a69
lib/trivial: add a few examples of usage of assertMsg/assertOneOf
Profpatsch eca136a
lib: move assertMsg and assertOneOf to their own library file
Profpatsch File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
{ lib }: | ||
|
||
rec { | ||
|
||
/* Print a trace message if pred is false. | ||
Intended to be used to augment asserts with helpful error messages. | ||
|
||
Example: | ||
assertMsg false "nope" | ||
=> false | ||
stderr> trace: nope | ||
|
||
assert (assertMsg ("foo" == "bar") "foo is not bar, silly"); "" | ||
stderr> trace: foo is not bar, silly | ||
stderr> assert failed at … | ||
|
||
Type: | ||
assertMsg :: Bool -> String -> Bool | ||
*/ | ||
# TODO(Profpatsch): add tests that check stderr | ||
assertMsg = pred: msg: | ||
if pred | ||
then true | ||
else builtins.trace msg false; | ||
|
||
/* Specialized `assertMsg` for checking if val is one of the elements | ||
of a list. Useful for checking enums. | ||
|
||
Example: | ||
let sslLibrary = "libressl" | ||
in assertOneOf "sslLibrary" sslLibrary [ "openssl" "bearssl" ] | ||
=> false | ||
stderr> trace: sslLibrary must be one of "openssl", "bearssl", but is: "libressl" | ||
|
||
Type: | ||
assertOneOf :: String -> ComparableVal -> List ComparableVal -> Bool | ||
*/ | ||
assertOneOf = name: val: xs: assertMsg | ||
(lib.elem val xs) | ||
"${name} must be one of ${ | ||
lib.generators.toPretty {} xs}, but is: ${ | ||
lib.generators.toPretty {} val}"; | ||
|
||
} |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about
else throw "Assertion failed: ${msg}"
instead? Usingtrace
will log withlvlError
and thus might be filtered out (eg. on Hydra, where only C++ exceptions are captured),throw
on the other hand is fatal (at least until used withtryEval
, but the same can be used for assertions anyway, so no need toabort
).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a good improvement to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, how would that look in practice? Would it still be used like
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, the difference is just that
assert
here essentially becomes a no-op ifpred
doesn't match, becausethrow
already takes care of raising an error before the actual assertion fails.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then the API stays the same, I see. I think we should do that.