-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Enter debugger more reliably in let expressions and function calls
#9917
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
Merged
thufschmitt
merged 2 commits into
NixOS:master
from
9999years:enter-debugger-more-reliably
Feb 8, 2024
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
25 changes: 25 additions & 0 deletions
25
doc/manual/rl-next/enter-debugger-more-reliably-in-let-and-calls.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| --- | ||
| synopsis: The `--debugger` will start more reliably in `let` expressions and function calls | ||
| prs: 9917 | ||
| issues: 6649 | ||
| --- | ||
|
|
||
| Previously, if you attempted to evaluate this file with the debugger: | ||
|
|
||
| ```nix | ||
| let | ||
| a = builtins.trace "before inner break" ( | ||
| builtins.break "hello" | ||
| ); | ||
| b = builtins.trace "before outer break" ( | ||
| builtins.break a | ||
| ); | ||
| in | ||
| b | ||
| ``` | ||
|
|
||
| Nix would correctly enter the debugger at `builtins.break a`, but if you asked | ||
| it to `:continue`, it would skip over the `builtins.break "hello"` expression | ||
| entirely. | ||
|
|
||
| Now, Nix will correctly enter the debugger at both breakpoints. |
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Can't we just replace that by
and not add the formatting logic in
makeDebugTraceStacker?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.
Ah nvm, I didn't notice that
makeDebugTraceStackerwas already usinghintfmt, just with a hardcoded number of 2 elements 😬 .It makes sense to make it a bit more generic then
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.
This also colors "let" magenta like the other things in error messages.
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.
Oh, right :) This thing is still too magical for me