aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/rl-next/source-positions-in-errors.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual/rl-next/source-positions-in-errors.md')
-rw-r--r--doc/manual/rl-next/source-positions-in-errors.md44
1 files changed, 0 insertions, 44 deletions
diff --git a/doc/manual/rl-next/source-positions-in-errors.md b/doc/manual/rl-next/source-positions-in-errors.md
deleted file mode 100644
index a9de87f28..000000000
--- a/doc/manual/rl-next/source-positions-in-errors.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-synopsis: Source locations are printed more consistently in errors
-issues: 561
-prs: 9555
-credits: [9999years, horrors]
-category: Improvements
----
-
-Source location information is now included in error messages more
-consistently. Given this code:
-
-```nix
-let
- attr = {foo = "bar";};
- key = {};
-in
- attr.${key}
-```
-
-Previously, Nix would show this unhelpful message when attempting to evaluate
-it:
-
-```
-error:
- … while evaluating an attribute name
-
- error: value is a set while a string was expected
-```
-
-Now, the error message displays where the problematic value was found:
-
-```
-error:
- … while evaluating an attribute name
-
- at bad.nix:4:11:
-
- 3| key = {};
- 4| in attr.${key}
- | ^
- 5|
-
- error: expected a string but found a set: { }
-```