Repository navigation
docs: map Vulkan allocator layers and example responsibilities - #23
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Add concise file introductions explaining the allocator layers, CPU-only tests, and real-device examples, and link those layers from a README source map. Preserve existing API documentation and the setup-script introduction. All 17 maintained code files have a purpose comment; executable source lines are unchanged.
Validation with V 0.5.2 7647ce1 and isolated pinned Vulkan v3.2.0 / memory v1.4.0 dependencies: formatting, CI-equivalent file-based vet, all seven TinyCC test files, and all three Vulkan examples passed. Examples ran with Lavapipe and Vulkan validation enabled, including sustained churn (1536 allocations).
git diff --checkpassed. The newer local compiler reports a pre-existing formatting difference; the stable compiler matching CI passes. Windows and sanitizer checks remain with repository CI.