feat: add Decoder.UseNumber and the Number type

Assisted-by: GLM 5.3 Flash
2026-09-21 23:49:39 +02:00
parent 582222738b
commit ce0c1ebd9d
9 changed files with 320 additions and 4 deletions
@@ -46,6 +46,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
  (10000 levels, which no hand-written document approaches): a document that
  nests arrays or inline tables deeper used to run the stack out and is now
  rejected with a `SyntaxError` naming the limit.
+- `Decoder.UseNumber()` decodes the integers and floats of the document into
+  `Number`, which carries the literal the document wrote, so `0x1f`, `1_000`,
+  `+1.0` and `inf` survive a round trip with their spelling instead of the
+  normalised `31`, `1000` and `1.0`. Typed destinations take the evaluated
+  value as before, a `Number` field takes the literal, and `Marshal` writes a
+  `Number` back as its bare literal, rejecting one that is not a valid TOML
+  number.

 ### Changed