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

Move ArrayMarshaller and PointerArrayMarshaller to the v2 design #71978

Merged
merged 9 commits into from
Jul 12, 2022

Conversation

jkoritzinsky
Copy link
Member

@jkoritzinsky jkoritzinsky commented Jul 11, 2022

Remove the built-in custom array pinning code as we don't need it any more (it's implemented on the marshallers themselves with the static GetPinnableReference method)

Contributes to #70859

Remove the built-in custom array pinning code as we don't need it any more (it's implemented on the marshallers themselves with the static GetPinnableReference method)
@ghost
Copy link

ghost commented Jul 11, 2022

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

Issue Details

Remove the built-in custom array pinning code as we don't need it any more (it's implemented on the marshallers themselves with the static GetPinnableReference method)

Author: jkoritzinsky
Assignees: -
Labels:

area-System.Runtime.InteropServices, source-generator

Milestone: -

@dotnet-issue-labeler
Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@jkoritzinsky
Copy link
Member Author

The test failures are #71990 and a GC hole that is under investigation. I'm going to merge this in.

@jkoritzinsky jkoritzinsky merged commit b4dd16b into dotnet:main Jul 12, 2022
@jkoritzinsky jkoritzinsky deleted the array-marshaller-v2 branch July 12, 2022 04:49
@ghost ghost locked as resolved and limited conversation to collaborators Aug 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants