Parenthesize negative numbers in ToField
instances
#145
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.
Closes #143.
This also switches the
Scientific
instance to use aByteString
builder instead of aText.Lazy
builder. Lazy text dates back to 87135c1, when scientific-0.2.0.2 only provided that option. Now we require scientific >= 0.3.7.0, which also provides theByteString
builder. The alternative was to reimplementparenNegatives
for this instance, which also wouldn't be too bad.For types with signed zeros,
-0
isn't parenthesized. I wasn't sure how to detect it ("check whether the rendered value starts with-
" should work but breaking out ofBuilder
feels bad for performance?), and I'm not aware of any situation where-(0::type)
would be different than(-0)::type
. I could easily imagine I'm missing something though.