Add 'TryGetDataUnsafe' overload for 'IMemoryBufferReference' #1673
Conversation
This file contains 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
Sergio0694
changed the title
Sergio0694
force-pushed
the
user/sergiopedri/memory-buffer-reference-interop
branch
2 times, most recently
from
1dae81c to
65778c3
Compare
Sergio0694
force-pushed
the
user/sergiopedri/memory-buffer-reference-interop
branch
from
65778c3 to
528abcf
Compare
Sergio0694
force-pushed
the
user/sergiopedri/memory-buffer-reference-interop
branch
from
528abcf to
4cf15e5
Compare
manodasanW
approved these changes
Jul 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contributes to #1672
Users shouldn't need manual interop (and defining an interface) to get data out of an
IMemoryBufferReferenceobject. This PR adds a newWindowsRuntimeMarshalinterop API that does the same we're already doing forIBuffer.