Mark Skilbeck

FWIW, the error message has improved since the creation of this issue: ``` $ echo test.quil | qvm --log-level emerg --quiet ! ! ! Condition raised: At line 1: unexpected...

I wonder if this question should instead be: should the QVM respect certain `PRAGMA`s like `PRESERVE_BLOCK`? or otherwise should the QVM be configurable to preserve qubits. @stylewarning thoughts?

Background reading: https://www.youtube.com/watch?v=H4v7wddN-Wg

👋🏽 😿

never forget QVMaaS.

For context: it's not unthinkable that we would like to enable secure network communication between the QVM and a remote caller.

I’m not familiar enough with this kinda technology to see how it would fit together. Could describe a hypothetical setup that would solve the issue of secure communication with QVM?...

@mlxd I haven't verified this, but it might be the case that the `Makefile` was replaced by the script in `dqvm/scripts/build-dqvm2-sbcl`. Give that a shot.

Yeah that looks to be the case: https://github.com/rigetti/qvm/blob/bump-version-1.17.1/dqvm/Makefile

Ah! Congrats on getting that far 😃 A colleague was working on [improving the CL MPI bindings](https://github.com/marcoheisig/cl-mpi/pull/29). Though that particular PR seems to have stalled. Are you familiar with how...