piegames
65ce95d381
I absolutely want to go back to allowing them, I am strongly of the opinion that nothing should be special about NUL in a string, but this will have to wait until at least the GC rewrite, so for now the least I can do is to disarm this gun. Change-Id: Id14b6037bc8b274c6c60ad970b1c74d436fb62a7
1.1 KiB
1.1 KiB
synopsis, issues, cls, category, credits
| synopsis | issues | cls | category | credits | ||
|---|---|---|---|---|---|---|
| more deprecated features | Breaking Changes |
|
This release cycle features a new batch of deprecated (anti-)features.
You can opt in into the old behavior with --extra-deprecated-features or any equivalent configuration option.
cr-line-endings: Current handling of CR (\r) or CRLF (\r\n) line endings in Nix is inconsistent and broken, and will lead to unexpected evaluation results with certain strings. Given that fixing the semantics might silently alter the evaluation result of derivations, the only option at the moment is to disallow them alltogether. More proper support for CRLF is planned to be added back again in the future. Until then, all files must use\nexclusively.nul-bytes: Currently the Nix grammar allows NUL bytes (\0) in strings, and thus indirectly also in identifiers. Unfortunately, several core parts of the code base still work with NUL-terminated strings and cannot easily be migrated. Also note that it is still possible to introduce NUL bytes and thus problematic behavior via other means, those are tracked separately.