UnmanagedFunctionPointer doesn't require field names to be functional #10724
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
…. Fixing the doc to just state that the fields are optional.
vitek-karas
requested review from
AaronRobinsonMSFT and
jkoritzinsky
as code owners
Member
Author
|
@AaronRobinsonMSFT for review. |
ghost
added
the
dotnet-policy-service
bot
added
the
community-contribution
|
Learn Build status updates of commit 3551619: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
AaronRobinsonMSFT
approved these changes
Dec 5, 2024
Member
|
/cc @gewarren |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Summary
Fixing the doc to just state that the fields are optional.