Disallow qvector arguments for custom operations
#2454
Merged
Conversation
This file contains 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
Signed-off-by: Pradnya Khalate <[email protected]>
khalatepradnya
force-pushed
the
fix-issue-2452
branch
from
b6fc5b4 to
5ff555f
Compare
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
khalatepradnya
commented
Dec 6, 2024
khalatepradnya
changed the title
qvector argumentsqvector arguments
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
|
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
bettinaheim
approved these changes
Dec 11, 2024
bettinaheim
changed the title
qvector argumentsqvector arguments for custom operations
bettinaheim
pushed a commit
that referenced
this pull request
Dec 11, 2024
Signed-off-by: Pradnya Khalate <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix for issue #2452.
In a follow up, we will look into supporting some of the scenarios that currently raise an error. As is right now, they would not be properly executed, so we give an error until this is properly supported.