Aleks Kissinger

I ran into this error myself, and nearly made the same PR (without the nice unit tests of course...). Is this going to get merged at some point?

Hi @Qubit1718, Anyone can contribute to this issue during unitaryHACK, taking place 3-17 June. There is not formal allocation process, just be the first to have an accepted PR and...

@paultirleson has been working on integrating pyzx with the tensor network library quimb. Still somewhat of a WIP, but you might want to check out the new `to_quimb_tensor` method for...

Hi Srinjoy, That's great! This issue is part of the unitaryHACK hackathon, taking place 3-17 June. Anyone can contribute as individuals or in teams. See: https://unitaryhack.dev for how it works....

Already started this, on the branch [fresh-name-bb](/Quantomatic/quantomatic/tree/fresh-name-bb). Users will be able to mark a variable as "fresh" by wrapping it in square brackets. When a !-box is expanded, any square-bracket...

This is in the works. A temporary work-around is to create a version of your rule where the whole LHS and RHS are in a !-box. Make sure to add...

I'm struggling a bit to see the use-case for this, especially since rewriting would (currently) clobber this data. I'm not against more annotations, but I think this idea is too...

The only problem I could foresee with sticking this in the project is if you wish to share a quanto project with someone else. The "current ruleset" is essentially throwaway...

This was a tricky one! Now fixed on the qpc2018 branch (which I intend to merge back into integration shortly after the Practical). I'll close the issue after the merge.

The way we handle this in quanto (and in fact a fairly standard way) is to maintain an "undo stack". Each item on the stack contains a little description of...