[release/10.0] UnsafeAccessor - ambiguous name and signature match
#119974
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.
Backport of #119972 to release/10.0
/cc @AaronRobinsonMSFT
Customer Impact
The
UnsafeAccessorAttributedoesn't properly differentiate ambiguity for between the two signatures below. Both arevoid(*)(void)and in that case the generic calling convention isn't used to indicate distinct signatures.Customer reported in #119875.
Regression
This is regression from .NET 8 because we didn't support generics method with
UnsafeAccessorAttribute. When it was added in .NET 9, a test case was missed. A new test was added to validate this scenario.Testing
A test was added.
Risk
Low.