Proof Portal
jsonparser
ProbeLabs36 findings · 123 requirementsWhen GetFloat addresses a JSON number token that is parseable as a float64 value, the parser shall return the corresponding float64 result.
Specification
The requirement exactly as authored — its complete prose text and, where present, the formal FRETish sentence it compiles to.
When GetFloat addresses a JSON number token that is parseable as a float64 value, the parser shall return the corresponding float64 result. ArrayEachErr is the io.EOF-aware ArrayEach variant where the callback may stop iteration by returning an error; the returned count includes the element whose callback stopped iteration.
the parser shall always satisfy !addressed_value_is_number | !raw_number_token_is_float_parseable | returns_getfloat_value
Rationale & tags
Why this requirement exists, and how it is categorised.
Rationale & tags
Why this requirement exists, and how it is categorised.
GetFloat is the public floating-point accessor for callers that know the expected numeric type and still need defined failure behavior.
Verification & provenance
How this requirement was checked: the review trail, edit history, and the machine-analysis status terms (each ⓘ explains what it means).
Review
- Status
- approved
- Reviewer
- human:leonidbugaev
- Reviewed
- Apr 23, 2026, 00:00 UTC
History
- Created
- Apr 13, 2026, 17:10 UTC · human:cli
- Modified
- Apr 13, 2026, 17:14 UTC · human:cli
Obligations
What this requirement must witness to be considered satisfied — the required evidence, and the tests that discharge each one.
No obligations recorded for this requirement
Proof obligations are recorded once evidence is generated. None have been captured here yet — this is expected, not a gap in the requirement itself. A required class of evidence the requirement must witness — the bridge between the requirement existing and it being proven.
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
Formula evidence
The formal formula behind this requirement, the variables it is written over, and the tests that exercise it (each term is explained inline).
FRETish formula
the parser shall always satisfy !addressed_value_is_number | !raw_number_token_is_float_parseable | returns_getfloat_value
Variables
| Name | Type | Direction | Description |
|---|---|---|---|
| addressed_value_is_number | — | True when the addressed value is a JSON number token. | |
| raw_number_token_is_float_parseable | — | True when the addressed JSON number token can be parsed as a float64 value. | |
| returns_getfloat_value | — | True when GetFloat returns the addressed value as a float64. |
Witnesses· 4 scenarios total
- FuzzGetFloatNativefuzz_native_test.go:192
- TestMCDC_SYS_REQ_004_Row1_TriggerFalsemcdc_spec_witnesses_test.go:103exercises 1 condition scenario
- TestAdditionalFuzzHarnessCoveragemcdc_supplement_test.go:425
- TestTypedGetterEdgeErrorsmcdc_supplement_test.go:92
- TestGetFloatparser_test.go:1576exercises 3 condition scenarios
Its place
This requirement shown inside its trace neighbourhood — the parents it satisfies, the code and tests attached to it, and its findings.
Loading graph…
Trace evidence
The concrete artifacts linked to this requirement — implementing code, verifying tests, documents, and the findings raised against it.
Impact
Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.
Impact
Blast radius — if you change this requirement, what else may need re-checking, and what it in turn depends on.
If you change this
Files to re-check (3)
- aliases.goaliases.go
- fuzz.gofuzz.go
- parser.goparser.go
Tests to re-run (6)
- aliases_test.goaliases_test.go
- array_each_err_test.goarray_each_err_test.go
- fuzz_native_test.gofuzz_native_test.go
- mcdc_spec_witnesses_test.gomcdc_spec_witnesses_test.go
- mcdc_supplement_test.gomcdc_supplement_test.go
- parser_test.goparser_test.go
What this rests on
Parent requirements (1)
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.