Add validation that the StackBufferSize member exists when a stackalloc constructor exists. #125
Conversation
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
…oc constructor exists.
jkoritzinsky
added
the
area-DllImportGenerator
AaronRobinsonMSFT
approved these changes
Sep 26, 2020
jkoritzinsky
added a commit
to jkoritzinsky/runtime
that referenced
this pull request
Sep 20, 2021
…oc constructor exists. (dotnet/runtimelab#125) Commit migrated from dotnet/runtimelab@9e7e221
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
While working on a prototype of the non-blittable struct marshalling, I discovered that I forgot to add validation for the StackBufferSize member in the ManualTypeMarshallingAnalyzer.
This validates that the StackBufferSize constant exists when a stackalloc constructor exists as per the spec.