Directly serialize f32 #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bors bot
added a commit
that referenced
this pull request
Jan 21, 2018
81: Directly serialize f32 r=torkleyy a=pyfisch Currently f32 is serialized by converting to f64 first. [This results in some numbers printed with many decimal places that do not convey information](https://play.rust-lang.org/?gist=2d8e4ab9d5d8fe689fdb6490bb4721c5&version=stable). (A f32 can represent about 6 decimal places)
Build succeeded |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently f32 is serialized by converting to f64 first. This results in some numbers printed with many decimal places that do not convey information. (A f32 can represent about 6 decimal places)