KEMBAR78
[mono] Some UnsafeAccessorAttribute support for methods and constructors by lambdageek · Pull Request #88925 · dotnet/runtime · GitHub
Skip to content

Conversation

@lambdageek
Copy link
Member

Just the simple cases so far that don't require considering custom modifiers.

Contributes to #86040

@ghost ghost added the area-VM-meta-mono label Jul 14, 2023
@ghost ghost assigned lambdageek Jul 14, 2023
@lambdageek

This comment was marked as resolved.

@lambdageek lambdageek requested a review from fanyang-mono July 14, 2023 19:19
@lambdageek
Copy link
Member Author

I moved the CallAmbiguousMethod test to a separate testcase - in general the custom modifiers stuff in Mono is not done. Only exact matches are working.

@lambdageek
Copy link
Member Author

Also need to try out the new tests from #88268

@lambdageek
Copy link
Member Author

Pushed some fixes to match the behavior expected by the new tests from #88268

@lambdageek lambdageek force-pushed the unsafe-accessor-kind branch from 3b3a7e2 to b96bcdb Compare July 14, 2023 20:24
@lambdageek
Copy link
Member Author

There will be merge conflicts with #88268 the resolution is on https://github.com/lambdageek/runtime/tree/unsafe-accessor-kind-merge-vitek

lambdageek and others added 2 commits July 14, 2023 17:48
…AccessorsTests.cs

Co-authored-by: Aaron Robinson <arobins@microsoft.com>
…AccessorsTests.cs

Co-authored-by: Aaron Robinson <arobins@microsoft.com>
Copy link
Member

@fanyang-mono fanyang-mono left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

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.

3 participants