Xiu-zhe (Roger) Luo
Xiu-zhe (Roger) Luo
Fortunately, our simplifier just works for the follow composite blocks (multi-qubits blocks contains single qubits Paulis) ```julia julia> using YaoBlocks julia> g = chain(2, kron(X, chain(X, Y)), control(2, 1=>X)) nqubits:...
This is useful and this is not related to this issue, see #9. The point to use prod here is just because it's easy to implement. I think eventually these...
I don't see any potential errors, you can't construct/desctruct a Prod without operators.
The point of #9 is when someone really hit something, it's never too late to make things work. We can't make everything work with one go.
It's something required for simplify for now, if this is removed, it won't work at all. I don't think remove functionality is a good idea. The point is we could...
I can just remove Chain's pass so simplify only works for Prod. And add it back when we have time to implement one for Chain.
This printing should be a bug. I'll have a look when I'm back. Ok now */prod strictly corresponding to Prod, nothing else will create a Prod node implicitly. (It's just...
@GiggleLiu The printing is correct: ```julia julia> X * Y nqubits: 1, datatype: Complex{Float64} prod ├─ X gate └─ Y gate ``` I don't get ```julia prod |- X gate...
But this will mess up the following ```julia control(2, 1, 2=>X) * kron(X, Y) ``` which make sense for simplification and basis, etc. (they are Cliffords) and I don't think...
A better way could be ```julia @eachregister id begin if configs[id] == 1 1 => X end end ```