Announcing Lix 2.95 “Kakigōri”
51 points by intarga
51 points by intarga
I thought I had a pretty good grasp of the Nix language, what do you mean [ 00.123 ] parses as [ 0 0.123 ]!? Is there any other language that will parse 00.123 as two separate tokens like that?
I'm also not quite sure what the release notes mean about using dynamic attributes in rec sets. The full release note says the dynamic attributes evaluate after the rest of the set, which sounds like expected behavior to me since you can reference the recset attrs from the dynamic attributes. I'd love to see an explanation of what the problem behavior is supposed to be here. The test case from the change is
rec {
yep = "bar";
foo = yep;
${foo} = "awa";
}
and this looks fine to me? Is the argument supposed to be that evaluating keys shouldn't reference the recset attrs, only values should?
[ 00.123 ] parses as [ 0 0.123 ]
This should not be a warning but outright error and the code itself fixed lol
I thought I had a pretty good grasp of the Nix language, what do you mean [ 00.123 ] parses as [ 0 0.123 ]!? Is there any other language that will parse 00.123 as two separate tokens like that?
Does it really parse like that? I'd think it'd be a single numeral with two leading zeroes…
I can understand the examples they bring up with 0.00.0 (which, taking maximal munch into account, and the prior rule where a float doesn't need to be prefixed with a zero, would be 0.00 .0) but this would be quite surprising.