-
Notifications
You must be signed in to change notification settings - Fork 121
Broadcasting and slicing updates #2326
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
Draft
orpuente-MS
wants to merge
12
commits into
main
Choose a base branch
from
oscarpuente/qasm-follow-up
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2,344
−1,805
Draft
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
c190235
broadcasting
orpuente-MS 12f8fae
fix parsing and lowering of indexed idents
orpuente-MS 8a04ec0
update indexed_ident tests
orpuente-MS 14293f5
broadcasting edge case
orpuente-MS a80a5a6
update unit tests
orpuente-MS 4a8f3ff
remove empty lines
orpuente-MS c2596b4
unignore slicing tests
orpuente-MS d3ca004
box IdentOrIndexedIdent
orpuente-MS f549de4
allow broadcast with mixed registers and qubits
orpuente-MS 4c46ea9
array indexing (work in progress)
orpuente-MS 5c8fa54
zero range step error
orpuente-MS 32ba718
Merge branch 'main' into oscarpuente/qasm-follow-up
orpuente-MS File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
This lo span doesn't feel correct
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.
There is no right answer here since the source syntax is different from Q#'s syntax.
The idea is that this source code
will get compiled to
The span in your comment is the span of the expression being indexed. For example, if we are currently building
a[1][2][3]
, the expression being indexed isa[1][2]
. But in the source code this corresponds toa[1, 2
, and that's what I'm setting the span to, which doesn't feel as intuitive as in Q#, but it's a best effort solution. Let me know if you can think of something better.