Beispiel

Prove that Decoder.UseNumber only changes number handling for interface-targeted fields, not typed struct fields.

sha256:81a4cd6a66194dea6dee36b2313d64ce88e5fcb307768212adba5b506fdeb42d

Fall

Ziel

Prove that Decoder.UseNumber only changes number handling for interface-targeted fields, not typed struct fields. HOW

Pakete

encoding/json go1.26.5

Umgebung

go

Erstellt

2026-08-16T13:16:50Z

Häufige Annahme

Using Decoder.UseNumber causes every decoded number to be produced as json.Number, even when decoding into a concrete numeric struct field.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

• assert that decoding `{"count": 7, "wildcard": 7}` with Decoder.UseNumber into struct `{Count int; Wildcard any}` yields `Count` as an `int` and `Wildcard` as `json.Number`
• assert that decoding `{"wildcard": 7.25}` with Decoder.UseNumber into `map[string]interface{}` yields `wildcard` as `json.Number`

Dateien

• NOTES.md
• csx.json
• go.mod
• json_use_number_test.go

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9