Developer guide¶
These pages document the internals: what you need to drive real hardware from a QDAC program, and what you need to change this package.
| Topic | What you find there |
|---|---|
| Lowering onto hardware | The module layout, the registration hooks, what a platform does with each operation, and how to add a new one. |
| Contributing | The uv workflow, the lint and test gate, style rules, and the checklist for a change. |
The User guide covers the same operations from the caller's
side, and the API reference is generated from the
docstrings under src/, so the code and the reference move together.
This package is only the QDAC half. The AST, the .qp format, the capability
protocol, and the reference executor all live in the core DSL. Two of its
developer pages are the background for everything here:
building a vendor extension
is the template this package follows, and
capability protocol internals
is the normative account of tokens, slots and predicates.