Don't panic when String() is called on nil Value{} #86
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.
While a
Value
without atyp
will not be returned fromNewValue
except in case of error,Value{}
is likely to appear in consumer code from time to time, e.g. in tests, as it is the nil value of the struct.This PR defines an arbitrary string representation for
Value{}
. The only non-trivial question here is what it should be.Backwards-compatible because this was previously undefined behaviour.
Bonus
This PR also adds lots of tests for
Value.String()
, which had little test coverage.