Manually write binding for Surface.getCapabilities #7
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.
The C usage pattern for this function is idiosyncratic:
you're expected to create a
WGPUSurfaceCapabilities
, pass a pointer to it towgpuSurfaceGetCapabilities(...)
,which then sets internal pointers to arrays along with their element counts.
You do not own these arrays, instead when you're done you're expected to
free them with a separate function
wgpuSurfaceCapabilitiesFreeMembers
which takes the capabilitiesstruct by value and frees the internal pointers.
This is the only function in the API that works remotely like this so the binding has to be hand-written.