From b87e1af31b7844eeb25858343cdefdfdcef26b5b Mon Sep 17 00:00:00 2001 From: Martin Tournoij Date: Fri, 24 May 2024 16:48:15 +0100 Subject: [PATCH] Add comment about int64 being optional --- README.md | 4 ++++ tests/valid/integer/long.toml | 4 +++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6762fec..dd8f301 100644 --- a/README.md +++ b/README.md @@ -200,6 +200,10 @@ Untested and implementation-defined behaviour This only tests behaviour that's should be true for every encoder implementing TOML; a few things are left up to implementations, and are not tested here. +- TOML does not mandate a specific integer or float size, but recommends int64 + and float64, which is what this tests. You'll have to manually -skip these + tests if your implementation doesn't support it. + - Many values can be expressed in more than one way: for example `0xff` and `255` are equal, as are `0.0` and `-0.0`. diff --git a/tests/valid/integer/long.toml b/tests/valid/integer/long.toml index 5db5ed7..6d0f928 100644 --- a/tests/valid/integer/long.toml +++ b/tests/valid/integer/long.toml @@ -1,2 +1,4 @@ -int64-max = 9223372036854775807 +# int64 "should" be supported, but is not mandatory. It's fine to skip this +# test. +int64-max = 9223372036854775807 int64-max-neg = -9223372036854775808