Add floating-point internal bit representation to TypeInfo #1139
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.
This makes writing floating-point generic code easier if it works with the internal bit representation.
Note that 80-bit extended precision floats may have a slightly different internal representation to all other types and according to IEEE this may be implementation defined. It currently is set to the most likely representation. We typically don't accept long doubles in the current math functions so can see how this plays out in practice, special casing if needed.
https://en.wikipedia.org/wiki/Extended_precision#x86_extended_precision_format