-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Use 'ref readonly' in 'Unsafe.AsPointer' #114406
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
Use 'ref readonly' in 'Unsafe.AsPointer' #114406
Conversation
Note regarding the
|
1 similar comment
Note regarding the
|
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 reviewed 6 out of 6 changed files in this pull request and generated no comments.
Tagging subscribers to this area: @dotnet/area-system-runtime-compilerservices |
Failure in |
ToolsTests legs are failing: #114406 (comment) Psychic debugging (without actually trying to repro anything) tells me this is from #114346 that makes us emit more dynamic keyword warnings. That PR didn't trigger the ToolsTests leg since it's not a ILLink change.
Likely fallout from a different PR that didn't run the Tools_Tests leg. Attempted a fix at #114424. |
ToolsTests legs are failing: #114406 (comment) Psychic debugging (without actually trying to repro anything) tells me this is from #114346 that makes us emit more dynamic keyword warnings. That PR didn't trigger the ToolsTests leg since it's not a ILLink change.
4c7f63d
to
6d3a3b9
Compare
Closes #114189
This PR updates the signature of
Unsafe.AsPointer
to take aref readonly
instead.