Repository navigation
Clarify IEEE 754 compliance for floating-point types and decimal - #56612
Merged
BillWagner merged 1 commit intoOct 27, 2026
Merged
Conversation
dotnet-policy-service
Bot
added
okr-quality
now.
BillWagner
enabled auto-merge (squash)
October 27, 2026 12:38
This file contains hidden or 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
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.
Summary
Clarifies IEEE 754 compliance in the floating-point numeric types reference:
floatanddoubleconform to the IEEE 754 binary floating-point specifications (binary32andbinary64).decimalis not an IEEE 754 floating-point format (such asdecimal128), does not support NaN or infinity, and represents decimal numbers using a 96-bit integer mantissa scaled by a power of 10.Fixes #33523
Internal previews
Build report