-
Notifications
You must be signed in to change notification settings - Fork 167
Soften .NET 12 language to reflect uncertainty in opt-in/opt-out behavior #357
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.
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
Conversation
Co-authored-by: agocke <515774+agocke@users.noreply.github.com>
Co-authored-by: agocke <515774+agocke@users.noreply.github.com>
Co-authored-by: agocke <515774+agocke@users.noreply.github.com>
| * 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also note that we have not settled on a .NET 12 behavior (opt in or opt-out)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to explicitly note that we have not settled on whether .NET 12 will be opt-in or opt-out by default. (commit 4d943bf)
Co-authored-by: agocke <515774+agocke@users.noreply.github.com>
| 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot please apply suggest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applied the suggestion. (commit 5c0a06d)
Co-authored-by: agocke <515774+agocke@users.noreply.github.com>
* 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 <515774+agocke@users.noreply.github.com> * Improve readability by breaking long sentence into shorter ones Co-authored-by: agocke <515774+agocke@users.noreply.github.com> * Further improve readability with shorter sentences Co-authored-by: agocke <515774+agocke@users.noreply.github.com> * Clarify that .NET 12 opt-in/opt-out behavior is undecided Co-authored-by: agocke <515774+agocke@users.noreply.github.com> * Apply suggestion to clarify opt-in first, then aspiration for opt-out Co-authored-by: agocke <515774+agocke@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: agocke <515774+agocke@users.noreply.github.com> --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.