Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move Clifford Tableau Out of cirq/sim/clifford folder
See original GitHub issueDescription of the issue
Clifford Tableau is used in the Clifford simulator. Except the simulation usage, Clifford tableau can also be used to represent a general n-qubit Clifford gates, which is not supported in cirq yet. This means we need to import tableau in the ops files to define general clifford gates. However, to avoid circular import issue, cirq/sim is not supposed to be imported in the top level of cirq/ops files. As discussed in cirq-cynq meeting, the easiest solution is move the Clifford Tableau out of cirq/sim folder. (Partially, also because Clifford Tableau itself is just a state representation not simulation.)
Question is where should we move it into? cirq/qis or cirq/value seems to be the good place.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We have in the
_compatmodule things for this,@deprecatedfor functions,@deprecated_classfor classes for example. I would recommend doing the deprecation just in case someone is using the submodule import path, it’s pretty cheap in the end.If users usually just import all of cirq that’s fine. If users frequently import submodules individually then this could cause breakages.