4de09b6b54
This version changes the handling of TOML timestamps, and throws an error on out‐of‐range integer literals rather than the previous saturating behaviour, as required by [the TOML v1.0.0 specification]: > Arbitrary 64-bit signed integers (from −2^63 to 2^63−1) should be > accepted and handled losslessly. If an integer cannot be represented > losslessly, an error must be thrown. [the TOML v1.0.0 specification]: <https://toml.io/en/v1.0.0#integer> The only known use of this is a questionable Nixpkgs test that I have proposed [a fix] for. [a fix]: <https://github.com/NixOS/nixpkgs/pull/433710> Bumping this ahead of Nixpkgs ensures we can test these cases on HEAD in advance. I presume that the next Lix major version will be released after 25.05 goes out of support, so it should be fine to drop support for the old version of toml11. The co‐authors of this commit are the contributors to the vendored package definition from Nixpkgs. Co-authored-by: Anderson Torres <torres.anderson.85@protonmail.com> Co-authored-by: Artturin <Artturin@artturin.com> Co-authored-by: Silvan Mosberger <silvan.mosberger@moduscreate.com> Change-Id: I6a6a69644a188b6e09eee5c9cf91ddd3c81d24ee
14 lines
430 B
Plaintext
14 lines
430 B
Plaintext
error:
|
|
… while calling the 'fromTOML' builtin
|
|
at /pwd/in.nix:1:1:
|
|
1| builtins.fromTOML ''attr = 9223372036854775808''
|
|
| ^
|
|
2|
|
|
|
|
error: while parsing TOML: [error] toml::parse_dec_integer: too large integer: current max digits = 2^63
|
|
--> fromTOML
|
|
|
|
|
1 | attr = 9223372036854775808
|
|
| ^-- must be < 2^63
|
|
|