Skip to content
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

Make sure we emit diagnostics for "unsupported" marshalling for downlevel platforms #71342

Merged
merged 2 commits into from
Jun 27, 2022

Conversation

jkoritzinsky
Copy link
Member

Separate out the "no marshalling info" error factory from the "unsupported" marshalling factory so we still get the same diagnostics on downlevel platforms where we use the forwarder as our fallback.

Fixes #71315

…evel platforms

Separate out the "no marshalling info" error factory from the "unsupported" marshalling factory so we still get the same diagnostics on downlevel platforms where we use the forwarder as our fallback.

Fixes dotnet#71315
@ghost
Copy link

ghost commented Jun 27, 2022

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

Issue Details

Separate out the "no marshalling info" error factory from the "unsupported" marshalling factory so we still get the same diagnostics on downlevel platforms where we use the forwarder as our fallback.

Fixes #71315

Author: jkoritzinsky
Assignees: -
Labels:

area-System.Runtime.InteropServices

Milestone: -

@jkoritzinsky
Copy link
Member Author

Failure is NativeAOT timeout

@jkoritzinsky jkoritzinsky merged commit d99caf1 into dotnet:main Jun 27, 2022
@jkoritzinsky jkoritzinsky deleted the fixes/71315 branch June 27, 2022 20:58
@ghost ghost locked as resolved and limited conversation to collaborators Jul 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants