Skip to content

Conversation

verult
Copy link
Collaborator

@verult verult commented Jun 15, 2022

@verult verult requested a review from tanujkhattar June 15, 2022 22:32
@verult verult requested review from wcourtney, a team, vtomole and cduck as code owners June 15, 2022 22:32
@CirqBot CirqBot added the size: L 250< lines changed <1000 label Jun 15, 2022
@verult verult requested a review from MichaelBroughton June 15, 2022 22:36
Copy link
Collaborator

@MichaelBroughton MichaelBroughton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, after updating the examples.

@MichaelBroughton MichaelBroughton added the automerge Tells CirqBot to sync and merge this PR. (If it's running.) label Jun 15, 2022
@CirqBot CirqBot added the front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. label Jun 15, 2022
@CirqBot CirqBot merged commit 8fbae53 into quantumlib:master Jun 15, 2022
@CirqBot CirqBot removed automerge Tells CirqBot to sync and merge this PR. (If it's running.) front_of_queue_automerge CirqBot uses this label to indicate (and remember) what's being merged next. labels Jun 15, 2022
@tanujkhattar
Copy link
Collaborator

@verult Ideally, we need to create google-specific versions of cz and sqrt-iswap target gatesets, which correctly handle wait gates and have additional postprocess transformers like eject_z and eject_phased_paulis.

It would be good to evaluate whether the proposed fix (i.e. using cirq.optimize_for_target_gateset with cirq-core gatesets) will be end up breaking the users flow who depend upon cg.optimized_for_sycamore or not. One way to evaluate this would be to rewrite the existing tests of cg.optimized_for_sycamore using cirq.optimize_for_target_gateset as well.

@verult
Copy link
Collaborator Author

verult commented Jun 20, 2022

Sounds good. I'm focusing on SerializableDevice and SerializableGateSet deprecations for the time being (the scope is growing larger than I anticipated). Not sure if I can get to this before the release deadline, but will take a look right after deprecations are done.

@verult
Copy link
Collaborator Author

verult commented Jun 24, 2022

@MichaelBroughton and I chatted about this and we decided to postpone the evaluation until after the 0.15 release.

If tests break, we could perhaps make a patch release to update the deprecation warning if it's not too time consuming to do.

@verult verult mentioned this pull request Jul 7, 2022
40 tasks
rht pushed a commit to rht/Cirq that referenced this pull request May 1, 2023
* Added deprecation warnings
* Updated tests to check for deprecation warnings.
@tanujkhattar @MichaelBroughton
harry-phasecraft pushed a commit to PhaseCraft/Cirq that referenced this pull request Oct 31, 2024
* Added deprecation warnings
* Updated tests to check for deprecation warnings.
@tanujkhattar @MichaelBroughton
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size: L 250< lines changed <1000
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants