-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
rethrow
primop
#8689
Comments
How should the stack trace behave?
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-07-31-nix-team-meeting-minutes-76/31486/1 |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/2023-09-22-nix-team-meeting-minutes-88/33343/1 |
I remember talking with Robert about how the proposed Since this isn't a high-priority feature, I won't be attempting this myself for now though (and I hope Robert won't either), there's better things to focus on imo :) |
Triaged in Nix team meeting 2023-09-22: idea approved to add as experimental feature |
Is your feature request related to a problem? Please describe.
The error message can not be touched
tryEval
must be independent of evaluation order #8688However, in many cases, users just want to add some info to the message.
In other cases, they may want to combine messages.
Both can be done without making evaluation order dependent.
Describe the solution you'd like
builtins.rethrow
such thatcauses the error
If they care about the value when successful, they can use a
let
binding to retrieve it.Describe alternatives you've considered
Alternatively or additionally, a list could be supported instead of an attrset.
We could allow arbitrary values in the exception message, which would be
printValue
d if they bubble up without getting changed back to a string.Poison pill string context #8388
Structured markup for
throw
andtrace
messages that make Nix more robust #7795Additional context
Priorities
Add 👍 to issues you find important.
The text was updated successfully, but these errors were encountered: