Xiu-zhe (Roger) Luo
Xiu-zhe (Roger) Luo
actually `@register id ` might be better
we have `@barrier` now, but might still something else.
suggested by @GiggleLiu , a better way to support this is via a primitive `expect`, which is equivalent to ```jl ob = 0 for _ in 1:nshots ob += @measure...
you need to `using YaoCompiler.Intrinsics` first, or you won't have the definition of `X`, with the `ccx` case, e.g ```julia using YaoCompiler using YaoCompiler.Intrinsics qasm"""OPENQASM 2.0; include "qelib1.inc"; """ @device...
for other examples you can check the tests first, the tests should be working at least.
actually some other code won't work due to wrong constant prop at the moment, I'm fixing it in #3
In principle, yes, but we need to make it more stable before we use it for testing. We can also add a downstream test for YaoCompiler later.
actually, I think we can just do a downstream test after integration with YaoCompiler, that's the easiest way of doing it.
FYI you don't have to use the package env for notebooks, every Pluto notebook has its own env by default.