diff options
author | Eelco Dolstra <edolstra@gmail.com> | 2020-09-01 10:31:17 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-09-01 10:31:17 +0200 |
commit | b721877b85bbf9f78fd2221d8eb540373ee1e889 (patch) | |
tree | 4c0d54f611c48dfbd38aecacb7ad4a124d96e4fc /doc/manual/src/release-notes/rl-1.6.1.md | |
parent | ebb8e076eb41e712be2eff51fbde971ddddda1ee (diff) | |
parent | 50f46836f3b1f8d45a3939611637041b24b656c3 (diff) |
Merge pull request #3857 from edolstra/markdown
Convert manual to Markdown
Diffstat (limited to 'doc/manual/src/release-notes/rl-1.6.1.md')
-rw-r--r-- | doc/manual/src/release-notes/rl-1.6.1.md | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/manual/src/release-notes/rl-1.6.1.md b/doc/manual/src/release-notes/rl-1.6.1.md new file mode 100644 index 000000000..9bb9bb1f8 --- /dev/null +++ b/doc/manual/src/release-notes/rl-1.6.1.md @@ -0,0 +1,32 @@ +# Release 1.6.1 (2013-10-28) + +This is primarily a bug fix release. Changes of interest are: + + - Nix 1.6 accidentally changed the semantics of antiquoted paths in + strings, such as `"${/foo}/bar"`. This release reverts to the Nix + 1.5.3 behaviour. + + - Previously, Nix optimised expressions such as `"${expr}"` to *expr*. + Thus it neither checked whether *expr* could be coerced to a string, + nor applied such coercions. This meant that `"${123}"` evaluatued to + `123`, and `"${./foo}"` evaluated to `./foo` (even though `"${./foo} + "` evaluates to `"/nix/store/hash-foo "`). Nix now checks the type + of antiquoted expressions and applies coercions. + + - Nix now shows the exact position of undefined variables. In + particular, undefined variable errors in a `with` previously didn't + show *any* position information, so this makes it a lot easier to + fix such errors. + + - Undefined variables are now treated consistently. Previously, the + `tryEval` function would catch undefined variables inside a `with` + but not outside. Now `tryEval` never catches undefined variables. + + - Bash completion in `nix-shell` now works correctly. + + - Stack traces are less verbose: they no longer show calls to builtin + functions and only show a single line for each derivation on the + call stack. + + - New built-in function: `builtins.typeOf`, which returns the type of + its argument as a string. |