Generate forwarder if all parameters can't be marshaled in LibraryImport#104246
Closed
jtschuster wants to merge 1 commit intorelease/8.0from
Closed
Generate forwarder if all parameters can't be marshaled in LibraryImport#104246jtschuster wants to merge 1 commit intorelease/8.0from
jtschuster wants to merge 1 commit intorelease/8.0from
Conversation
Contributor
|
Tagging subscribers to this area: @dotnet/interop-contrib |
Contributor
|
@jtschuster friendly reminder that code complete for the August Release is July 15th. If you want this fix to be included in that release, please merge this PR before that date. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I was wondering why I couldn't repro a partially generated LibraryImport to test #103973. It's because we have this code in main that will generate a forwarder if we can't generate marshaling for all parameters. I haven't been able to test this, but this might be a simpler fix for the issue we were hitting.