Soften .NET 12 language to reflect uncertainty in opt-in/opt-out behavior #357
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
Co-authored-by: agocke <[email protected]>
Co-authored-by: agocke <[email protected]>
Co-authored-by: agocke <[email protected]>
agocke
reviewed
Dec 16, 2025
| * In .NET 11, the feature will be off-by-default and in preview, and we will not be recommending broad adoption by arbitrary users until we have collected more | ||
| usability feedback and dialed in the enforcement. Users will be able to opt-in to the feature preview by putting `<MemorySafetyRules>preview</MemorySafetyRules>` | ||
| into their project files. | ||
| * In the .NET 12 or 13 timeframe, once we have the ecosystem experience that we are fully confident in, we will have an opt-in flag `<MemorySafetyRules>2</MemorySafetyRules>`. Users that take no action will see no changes. |
Member
There was a problem hiding this comment.
Please also note that we have not settled on a .NET 12 behavior (opt in or opt-out)
Contributor
Author
There was a problem hiding this comment.
Updated to explicitly note that we have not settled on whether .NET 12 will be opt-in or opt-out by default. (commit 4d943bf)
Copilot
AI
changed the title
[WIP] Update documentation for memory safety based on feedback
Soften .NET 12 file-based programs language to reflect uncertainty
Dec 16, 2025
Co-authored-by: agocke <[email protected]>
Copilot
AI
changed the title
Soften .NET 12 file-based programs language to reflect uncertainty
Soften .NET 12 language to reflect uncertainty in opt-in/opt-out behavior
Dec 16, 2025
jkotas
reviewed
Dec 16, 2025
| usability feedback and dialed in the enforcement. Users will be able to opt-in to the feature preview by putting `<MemorySafetyRules>preview</MemorySafetyRules>` | ||
| into their project files. | ||
| * In the .NET 12 or 13 timeframe, once we have the ecosystem experience that we are fully confident in, we will have an opt-in flag `<MemorySafetyRules>2</MemorySafetyRules>`. Users that take no action will see no changes. | ||
| * In the .NET 12 or 13 timeframe, once we have the ecosystem experience that we are fully confident in, we will make the feature available via `<MemorySafetyRules>2</MemorySafetyRules>`. We have not yet settled on whether this will be opt-in or opt-out by default. |
Member
There was a problem hiding this comment.
Suggested change
| * In the .NET 12 or 13 timeframe, once we have the ecosystem experience that we are fully confident in, we will make the feature available via `<MemorySafetyRules>2</MemorySafetyRules>`. We have not yet settled on whether this will be opt-in or opt-out by default. | |
| * In the .NET 12 or 13 timeframe, once we have the ecosystem experience that we are fully confident in, we will make the feature available via `<MemorySafetyRules>2</MemorySafetyRules>`, first as an opt-in. Our aspiration is to enable the new memory safety rules by default with opt-out eventually. The approach will be informed by the ecosystem experience we gain with .NET 11. |
I think we can say where we would like to be.
Contributor
Author
There was a problem hiding this comment.
Applied the suggestion. (commit 5c0a06d)
Co-authored-by: agocke <[email protected]>
Copilot stopped work on behalf of
agocke due to an error
December 16, 2025 23:24
agocke
added a commit
that referenced
this pull request
Dec 16, 2025
* Update memory safety enforcement details in documentation Clarified opt-in and opt-out mechanisms for memory safety rules in .NET 11 and 12. * Soften .NET 12 language to reflect uncertainty in opt-in/opt-out behavior (#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]> --------- Co-authored-by: Copilot <[email protected]>
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.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.