Skip to content

Remove redundant unsafe context #116187

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

Merged
merged 1 commit into from
Jun 2, 2025
Merged

Conversation

EgorBo
Copy link
Member

@EgorBo EgorBo commented Jun 1, 2025

Removed in a semi-automated way, some places might require it back once "unsafe callers" is implemented (although, mostly as inner unsafe scopes, not modifiers).

@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jun 1, 2025
@EgorBo EgorBo added reduce-unsafe and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jun 1, 2025
@stephentoub
Copy link
Member

Is this basically "if the code continues to compile after removing unsafe, remove it"?

@EgorBo
Copy link
Member Author

EgorBo commented Jun 1, 2025

Is this basically "if the code continues to compile after removing unsafe, remove it"?

I was using R#'s 'remove redundant unsafe' inspection and the repo compiled locally

@am11 am11 added the area-Meta label Jun 1, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

@EgorBo EgorBo merged commit 8a62488 into dotnet:main Jun 2, 2025
150 checks passed
@EgorBo EgorBo deleted the remove-redundant-unsafe-3 branch June 2, 2025 15:17
@github-actions github-actions bot locked and limited conversation to collaborators Jul 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants