-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Merge master to release/dev16.9-preview1 #47927
Merge master to release/dev16.9-preview1 #47927
Conversation
We now support understanding the calling convention types specified in UnmanagedCallersOnlyAttribute when performing overload resolution on an address of a method group. For the purposes of such resolution, we use the rules from the function pointers spec https://github.com/dotnet/csharplang/blob/master/proposals/csharp-9.0/function-pointers.md#systemruntimeinteropservicesunmanagedcallersonlyattribute.
* Simplified the handling for bad expressions in UnmanagedCallersOnly data, it is now ignored. * Refactored UnmanagedCallersOnlyAttributeData to be a method with a forceComplete parameter, for better behavior with PEMethodSymbol. * Added and tweaked a couple of tests.
…l test refactorings.
…ly and regular the same, and simplify the comparisons.
…entions supplied to the CallConvTypes array.
* Simplified convention type checking * Fixed stackoverflow in attribute constructor overload resolution * Added more loop tests.
…ions Implement UnmanagedCallersOnly conversions support
…rFix Sort the code fix action for UnusedValueCodeFixProvider
…and Interlocked (#47523)
Hello @dotnet-bot! Because this pull request has the Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 12 minutes. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
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.
Auto-approval
This is an automatically generated pull request from master into release/dev16.9-preview1.
Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯
Troubleshooting conflicts
Identify authors of changes which introduced merge conflicts
Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:
Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.
Resolve merge conflicts using your local repo
Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.
git fetch --all git checkout merges/master-to-release/dev16.9-preview1 git reset --hard upstream/release/dev16.9-preview1 git merge upstream/master # Fix merge conflicts git commit git push upstream merges/master-to-release/dev16.9-preview1 --force