forked from lix-project/lix
jade
748d8310fa
This doesn't comprehensively fix everything outdated in the manual, or
make the manual greatly better, but it does note down where at least
jade noticed it was wrong, and it does fix all the instances of
referencing Nix to conform to the style guide to the best of our
ability.
A lot of things have been commented out for being wrong, and there are
three types of FIXME introduced:
- FIXME(Lix): generically Lix needs to fix it
- FIXME(Qyriad): re lix-project/lix#215
- FIXME(meson): docs got outdated by meson changes and need rewriting
I did fix a bunch of it that I could, but there could certainly be
mistakes and this is definitely just an incremental improvement.
Fixes: lix-project/lix#266
Change-Id: I5993c4603d7f026a887089fce77db08394362135
26 lines
596 B
Markdown
26 lines
596 B
Markdown
---
|
|
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
|
|
```
|
|
|
|
Lix 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, Lix will correctly enter the debugger at both breakpoints.
|