Open
Conversation
Collaborator
|
Do you first need the pyzx pr to be merged for this? I see that changed the edgetype imports to not import from pyzx |
Collaborator
Author
|
Yes I do need the PR. I originally introduced a new edge type into zxlive but I decided its best to put it in pyzx. I've reverted the import patterns now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
My plan is to add support for css fault equivalence analysis by adding an "unidealise edge" action, where the user then has to provide a valid fault equivalent rewrite for that edge.
Then we can extend this to sets of edges and include detecting region ideas.