-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Disallow empty measurement keys and fix tests using empty keys #4060
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Discussed offline - this may not be necessary if we choose to auto-convert keyless gates into qubit-named gates. Holding off on merge until @smitsanghavi confirms his decision. |
ping @95-martin-orion @smitsanghavi is this to be closed or pushed forward? |
Closing this as we had opted for a different solution (auto-convert "keyless" gates to qubit-based naming). If we need to revisit this (or decide that this PR was the correct choice) we can reopen this PR. |
Reviving this since we decided to revert the qubit based auto-naming. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. IIUC, all replace
calls go through the constructor, so any accidental clearing of key strings by remapping will be prevented.
…umlib#4060) * Empty keys are illegal now * merge * fix duplicate post-inits
…umlib#4060) * Empty keys are illegal now * merge * fix duplicate post-inits
Part of #4040