Add first draft of ZXTransformer to contrib.

[dlyongemallo]

This is a custom transformer which uses ZX-calculus through the PyZX library to perform circuit optimisation.

See issue #6585.

[NoureldinYosri]

@mhucka the contributer has indicated in the issue that they don't have time to work on this #6585 (comment)

[mhucka]

That's correct, but they asked if someone else could take it over; they didn't say to close it. Moreover, the associated issue is still open. Since this PR was auto-closed by bot due to staleness, it seems like the right action is to reopen it and at least have a discussion about whether both the issue and the PR should be closed deliberately.

[dstrain115]

@naerabati Are you still interested in doing work on the ZX calculus transformer? Want to pick this up?

[naerabati]

Sorry I couldn't answer earlier! I don't think right now I will have the time to finish the transformer either

[naerabati]

@dstrain115 @dlyongemallo would you be able to tell me what else needs to implemented to complete this PR?

[github-actions]

This pull request has been automatically labeled as stale because 90 days have passed without comments or other activity. If no further activity occurs and the status/stale label is not removed by a maintainer within 60 days, this pull request will be closed. If you would like to restore its active status, please leave a comment here; doing so will cause the staleness handler to remove the label.

If you have questions or feedback about this process, we welcome your input. You can open a new issue to let us know (please also reference this issue there, for continuity), or reach out to the project maintainers at quantum-oss-maintainers@google.com.

[github-actions]

This pull request has been automatically labeled as stale because 90 days have passed without comments or other activity. If no further activity occurs and the status/stale label is not removed by a maintainer within 60 days, this pull request will be closed. If you would like to restore its active status, please leave a comment here; doing so will cause the staleness handler to remove the label.

If you have questions or feedback about this process, we welcome your input. You can open a new issue to let us know (please also reference this issue there, for continuity), or reach out to the project maintainers at quantum-oss-maintainers@google.com.

[github-actions]

This pull request has been automatically labeled as stale because 90 days have passed without comments or other activity. If no further activity occurs and the status/stale label is not removed by a maintainer within 60 days, this pull request will be closed. If you would like to restore its active status, please leave a comment here; doing so will cause the staleness handler to remove the label.

If you have questions or feedback about this process, we welcome your input. You can open a new issue to let us know (please also reference this issue there, for continuity), or reach out to the project maintainers at quantum-oss-maintainers@google.com.

[github-actions]

This pull request has been automatically labeled as stale because 90 days have passed without comments or other activity. If no further activity occurs and the status/stale label is not removed by a maintainer within 60 days, this pull request will be closed. If you would like to restore its active status, please leave a comment here; doing so will cause the staleness handler to remove the label.

If you have questions or feedback about this process, we welcome your input. You can open a new issue to let us know (please also reference this issue there, for continuity), or reach out to the project maintainers at quantum-oss-maintainers@google.com.

[mhucka]

Closing due to inactivity.

[dlyongemallo]

I can actually pick this back up. I recently updated the change to use pyzx 0.10.0, which adds support for reset and measurement operations which were previously not available when this PR was first created.

What needs to be done from my end to get this merged?

[mhucka]

@dlyongemallo Thank you for your work. It looks like GitHub will not let me reopen this PR; I get an error message that the branch was "either force-pushed or recreated".

It's possible GitHub will let you reopen it. If the button to reopen the PR is available to you, go ahead and click it.

If it is not available, then the easiest thing to do would be to open a fresh PR. In the PR description, you can write something to the effect of "continuation of PR #6647" or something like that, to help people follow.

[dlyongemallo]

@mhucka I wasn't able to re-open this. I've opened a fresh PR #8026.