Q++ is C++ with a few honest patches under the hood — just enough to describe quantum bits and their logic where you need them, and nothing more. A systems programmer shouldn’t have to throw away everything they know to touch quantum computing. If you can write C++, you should be able to write for a quantum processor without learning an entirely new programming model. So Q++ extends the language you already have instead of replacing it.

Under that idea sit real design choices. You model classical and quantum pieces with qstruct, qclass, cstruct and cclass, and manage memory with qregister and cregister. You tell the runtime where work should go with task<QPU>, task<CPU>, task<AUTO> and task<MIXED>. Bitwise operators map to quantum gates — an ^ becomes a controlled-X — and when you want the metal you inject raw gate instructions with __qasm. There’s even an #explain directive that emits plain-English comments describing what the quantum instructions do, because readable code is trustable code.

The pipeline is two pieces. The compiler, qppc, parses Q++ into a typed intermediate representation carrying Quantum Intermediate Representation (QIR) metadata. The runtime, qpp-run, executes that IR on a wavefunction simulator today, with stubs in place to target real hardware through Qiskit, Cirq, Braket, Q#, NVIDIA and PsiQuantum. It’s an early prototype and I’m honest about that — partial C++ parsing, backends still stubbed, experimental control flow — but the compiler runs, the simulator runs, and the shape of the thing is real.

I built Q++ with AI as a tool, the same way a carpenter builds with a power drill. That doesn’t make it less mine to have made, and it doesn’t make it less yours to use. I put it on GitHub because a stranger should be able to read it in ten minutes and trust it — no hidden inputs, no dark corners, just an architecture you could have looked up yourself. Same principle behind the whole e-co project: readable, documented, honest about its limits. Build like brick, not straw, so when the weather turns it holds. So take it — fork it, break it, ship something with it.

If you want to follow the build — the compiler, the runtime, the e-co platform it all connects to — the repos are open and the door is open. That’s the whole idea.