[Panic] qsc_passes: `use _ = Qubit();`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- compilers, quantum-computing
Research direction
Start in source/compiler/qsc_passes/src/replace_qubit_allocation.rs at generate_qubit_alloc_stmts, where the panic occurs. Reproduce it by compiling the shown Q# operation through the eval harness and qubit-allocation pass; done means use _ = Qubit(); no longer panics and compilation proceeds successfully.
Written by the indexing model from the issue text.
Description
- Crate:
qsc_passes - Panic: replace_qubit_allocation.rs:86, in
generate_qubit_alloc_stmts - Stage / profile: compiling the source (harness
evalstep, qubit-allocation pass), Base - Message:
Shape of identifier pattern doesn't match shape of initializer
operation Main() : Unit {
use _ = Qubit();
}
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 219
- Avg merge
- 3d 8m
- Merged PRs (30d)
- 71
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/qdk
-
[Samples] Investigate redundant CheckMay be free again @theARCania claimed this 39 days ago, and no pull request is open. Openenhancement good first issue low-priority
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/qdk#1933 · 4 comments ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 47/100
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
[Panic] `adj specialization should exist`: `Adjoint` of a callable local after an early `return`Openbug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metasequoiaime/msime#9113 ·
Maintainers usually reply within 1 day
-
area:desktop priority:p2 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area: supply-chain
Difficulty 1/5 Under an hour Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Refresh stale docsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
OpenCarControls/firmware#35 ·