Skip to content

Fix lpVtbl field declaration when both explicit-vtbls and generate-marker interfaces are specified #363

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jul 30, 2022
Merged

Fix lpVtbl field declaration when both explicit-vtbls and generate-marker interfaces are specified #363

merged 2 commits into from
Jul 30, 2022

Conversation

@SeeminglyScience
Copy link
Contributor

Fixes #362

@tannergooding tannergooding merged commit ed9de28 into dotnet:main Jul 30, 2022
@SeeminglyScience SeeminglyScience deleted the SeeminglyScience/issue362 branch July 31, 2022 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tannergooding tannergooding tannergooding approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

lpVtbl field is missing generic arg when marker-interface and explicit-vtbls are both specified

2 participants

@SeeminglyScience @tannergooding