[docs] Document argument order for controlled rotation gates#4605
Open
aryanputta wants to merge 1 commit into
Open
[docs] Document argument order for controlled rotation gates#4605aryanputta wants to merge 1 commit into
aryanputta wants to merge 1 commit into
Conversation
For parameterized gates (rx, ry, rz, r1, u3), the gate parameters precede the control and target qubits when using .ctrl in Python or <cudaq::ctrl> in C++. Adds matching Python and C++ examples showing single- and multi-control rotations. Closes NVIDIA#2285 Signed-off-by: Aryan Putta <aryansputta@gmail.com>
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
1 participant
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.
Summary
Clarifies the argument order for controlled parameterized gates (
rx,ry,rz,r1,u3) in theAdjoint and Controlled Operationssection ofdefault_ops.rst. The convention (parameters first, then control qubits, then target) was not explicitly stated, which caused user confusion (see issue #2285).Change
Docs-only change; no code paths affected.
Closes #2285