You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there is now a test which explains vmaCopyMemoryToAllocation in detail (see pr #474), it might be worth to write one more tests which deals with vmaCopyAllocationToMemory. We could also embedd the actual code from that test in the docs then, instead of displaying uncompiled and untested code in the section "Recommended usage patterns".
The text was updated successfully, but these errors were encountered:
Agreed, this may be a good idea. However, I am not sure if a code taken from a test would look good in the documentation. Copy-paste with some modifications to improve the readability as a standalone code sample could work better.
Since there is now a test which explains vmaCopyMemoryToAllocation in detail (see pr #474), it might be worth to write one more tests which deals with vmaCopyAllocationToMemory. We could also embedd the actual code from that test in the docs then, instead of displaying uncompiled and untested code in the section "Recommended usage patterns".
The text was updated successfully, but these errors were encountered: