Update length/capacity exceptions for .NET 11#12212
Merged
gewarren merged 1 commit intodotnet:mainfrom Jan 12, 2026
Merged
Conversation
Contributor
|
Tagging subscribers to this area: @dotnet/area-system-io |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the MemoryStream documentation to reflect .NET 11 changes regarding length and capacity exceptions. The primary focus is documenting the new maximum value (0x7FFFFFC7 bytes) for capacity and length operations introduced in .NET 11.
Key changes include:
- Adding .NET 11-specific exception documentation for
Capacityproperty andSetLengthmethod - Fixing xref formatting by removing
.%2Asuffixes from property references - Improving documentation formatting and consistency
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.
Contributes to dotnet/docs#49545.