feat!: backport breaking changes from #479#482
Merged
antalsz merged 4 commits into456-feat-merge-cratesfrom Sep 26, 2025
Merged
feat!: backport breaking changes from #479#482antalsz merged 4 commits into456-feat-merge-cratesfrom
antalsz merged 4 commits into456-feat-merge-cratesfrom
Conversation
…he associated code
Previously, `MeasureCalibrationDefinition` contained an *optional* qubit and a *mandatory* memory address, rather than the other way around.
|
This PR has too many files to review (>50 files). |
|
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
2 participants
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.
This PR backports the following breaking changes from #479, as they're generally useful for #462 and we want to minimize the number of breaking change releases. The changes are as follows
quil_rs::program::MemoryAccesstype.Calibrationtype toCalibrationDefinitionfor consistency, along with some updates to associated code.MeasureCalibrationDefinitiontype to correctly have a required qubit and an optional memory address, rather than the other way around..snapfiles that no longer correspond to anything, so it needed to happen.