Skip to content

Document a behavior of string.Create #10619

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 30, 2024
Merged

Document a behavior of string.Create #10619

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fcc3a28
Document a behavior of string.Create
tannergooding Oct 30, 2024
c811318
Apply suggestions from code review
tannergooding Oct 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions xml/System/String.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4364,6 +4364,8 @@ The following example demonstrates the <xref:System.String.CopyTo%2A> method.
<format type="text/markdown"><![CDATA[
## Remarks
The initial content of the destination span passed to `action` is undefined. Therefore, it is the delegate's responsibility to ensure that every element of the span is assigned. Otherwise, the resulting string could contain random characters.

To support interop scenarios, the underlying buffer is guaranteed to be at least 1 greater than represented by the span parameter of the action callback. This additional index represents the null-terminator and, if written, that is the only value supported. Writing any value other than the null-terminator corrupts the string and is considered undefined behavior.
]]></format>
</remarks>
</Docs>
Expand Down