Skip to content

docs: explain Vulkan source boundaries and helper file purposes - #71

Merged
antono2 merged 2 commits into
masterfrom
docs/file-guidance-20261007
Oct 7, 2026
Merged

antono2 merged 2 commits into
masterfrom
docs/file-guidance-20261007

Conversation

@antono3

@antono3 antono3 commented Oct 7, 2026 •

Copy link
Copy Markdown
Collaborator

Add purpose comments to handwritten loader, ergonomic resource helpers, tests and CI probes, plus a maintainer source map. Regenerate both public binding introductions through antono2/v_vulkan_bindings#22 using Vulkan-Docs v1.4.365 at 8c9361ba8180c1f4164c0bf79de2f6e817770b0d.

Compared the complete regenerated files with the prior snapshots: only the three-line introductions differ; every declaration is unchanged. Clarify that REGISTRY_COMMIT pins Vulkan-Headers, while VERSION selects the Vulkan-Docs generation tag. Vendor headers and dependency pins are unchanged.

Validation: both targets regenerate and format with stable V; exact comparison excluding the emitted introduction passes. Shell syntax, local documentation links and git diff --check pass. Earlier CI was green; rebuilt platform checks are pending on the new head.

@antono2
antono2 merged commit 28a5577 into master Oct 7, 2026
8 checks passed
@antono2
antono2 deleted the docs/file-guidance-20261007 branch October 7, 2026 09:59
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

Successfully merging this pull request may close these issues.

2 participants