Skip to content

Write a new test which covers readback using vmaCopyAllocationToMemory? #476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
IAmNotHanni opened this issue Apr 1, 2025 · 1 comment

Comments

@IAmNotHanni
Copy link
Contributor

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".

@adam-sawicki-a
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants