Decode: fail when array is missing separator #616
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #613
The toml-test generated test for an array with missing separators was
failing since the parser wasn't noticing missing separators.
This change leverages the zero value of
ast.Reference
(anint
). Thevar is now declared outside the while block, and re-zeroed if the
token is not a non-trailing comma.
The parser checks if the previous value of
valueRef
is zero. Theonly time this check would pass is when the previous byte in the array
was a whitespace, which would only be the case when an array is
missing a separator.
Fixes
go test -tags testsuite -run TestTOMLTest_Invalid_Array_MissingSeparator