Update BitConverter.xml #9809
Merged
Update BitConverter.xml #9809
Conversation
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
Update remarks table for class-level documentation
dotnet-policy-service
bot
added
the
community-contribution
ghost
added
the
|
Learn Build status updates of commit 21e644e: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Tagging @dotnet/area-system-runtime. |
tannergooding
approved these changes
Apr 15, 2024
|
Thanks @colejohnson66 |
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.
Update the remarks table for class-level documentation.
Summary
Added
XToUIntXXBitsandUIntXXBitsToXmethod mentions forSingleandDouble, and added a row forHalf. Also added some spacing in table source for ease of editing in the future.Questions
With
TryWriteBytes(Span<byte>, T)now existing, this table could further be altered to include a "serialize to bytes" column. Is this desired?Alternatively, due to the expanding API surface, it could be argued that this table should just be removed?