Expose reflective QBS generation - #71
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
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.
Expose the existing QBS v1 reflective build mode through quarry-schema-compiler.
Minimal (default):
Reflective:
Reflective QBS includes record display names, field names, and enum type names. Symbolic enum-value names remain unsupported. Minimal QBS remains the default for compatibility and smaller embedded metadata.
For benchmarks/schemas/workload.brd, measured artifacts were:
The resulting workflow is
.brd -> quarry-schema-compiler --emit-qbs --qbs-reflective -> reflective QBS -> quarry-brf-inspect -> human-readable field names.This uses existing
BuildMode::Reflective,QbsModelBuilder, and QBS v1 serialization. No QBS/BRF/Schema IR format changes or compatibility bumps are required.Compatibility: C++ epoch 3, C epoch 2, Python epoch 1, BRF 2, QBS 1.
Validation: focused schema compiler tests, QBS model/serializer/parser tests, full CTest 53/53, deterministic generation, and reflective end-to-end inspection passed.