Update memory safety enforcement details in documentation #356
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
Clarified opt-in and opt-out mechanisms for memory safety rules in .NET 11 and 12.
jkotas
reviewed
Dec 16, 2025
| For .NET 11, the new rules are not on by default. Users will be able to opt-in to the preview by adding `#:property MemorySafetyRules=preview` to their `.cs` files. | ||
|
|
||
| In .NET 12, we enable the new rules by default for file-based programs. Users that wish to opt-out of the new rules can do so by adding `#:property MemorySafetyRules=1` | ||
| In .NET 12, file-based programs will behave differently from projects. We enable the new rules by default for file-based programs. Users that wish to opt-out of the new rules can do so by adding `#:property MemorySafetyRules=1` |
Member
There was a problem hiding this comment.
I do not think this plan is set in stone. We will learn a ton between now and then. Should this say that this is our current aspiration?
Member
Author
There was a problem hiding this comment.
I think you nailed it: I really don't think any of our plans are set in stone. Should we just say that we don't know?
Member
There was a problem hiding this comment.
Perhaps that would be best; certainly the decisions we made at the sdk meeting were not "let's force every template to change to opt-in all new projects by default".
4 tasks
Contributor
…vior (#357) * Initial plan * Update .NET 12 file-based programs plan to reflect uncertainty Co-authored-by: agocke <[email protected]> * Improve readability by breaking long sentence into shorter ones Co-authored-by: agocke <[email protected]> * Further improve readability with shorter sentences Co-authored-by: agocke <[email protected]> * Clarify that .NET 12 opt-in/opt-out behavior is undecided Co-authored-by: agocke <[email protected]> * Apply suggestion to clarify opt-in first, then aspiration for opt-out Co-authored-by: agocke <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: agocke <[email protected]>
jkotas
approved these changes
Dec 16, 2025
333fred
approved these changes
Dec 16, 2025
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.
Clarified opt-in and opt-out mechanisms for memory safety rules in .NET 11 and 12.