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

Don't pin managed collection objects when the contents are non-blittable. #69696

Merged
merged 6 commits into from
May 27, 2022

Conversation

jkoritzinsky
Copy link
Member

We need to make sure we marshal the elements of the collection always.

@ghost
Copy link

ghost commented May 23, 2022

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

Issue Details

We need to make sure we marshal the elements of the collection always.

Author: jkoritzinsky
Assignees: -
Labels:

area-System.Runtime.InteropServices

Milestone: -

…erop.SourceGeneration/Marshalling/AttributedMarshallingModelGeneratorFactory.cs

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

QUIC test failures are #69792.
GC test failure is #65183
WASM failure is #69806
JITStress failure is unrelated.

@jkoritzinsky jkoritzinsky merged commit 554aa54 into dotnet:main May 27, 2022
@jkoritzinsky jkoritzinsky deleted the managed-pinning-blittable branch May 27, 2022 17:20
@ghost ghost locked as resolved and limited conversation to collaborators Jun 26, 2022
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