`for` loops only accept sets and ranges — not `bit[n]`, arrays, aliases or index expressions
维护者通常 1 天内回复
评估
调研方向
Start in Qasm3Visitor._visit_forin_loop at src/pyqasm/visitor.py (around line 2462), where the type check on statement.set_declaration rejects everything except DiscreteSet and RangeDefinition. Move that branch into a helper that returns a list of values, then add the array case first, since it doesn't depend on other work. Done when tests/qasm3/test_loop.py covers each iterable form and an index expression, a write to the loop variable leaves the source array unchanged, and a multi-dimensional array raises ValidationError.
由索引模型根据 Issue 内容生成。
描述
Limitation
For loops states that the iterated <values> may
be any of:
- a discrete set, e.g.
{1, 2, 3} - a range expression, e.g.
[0:2:10] - a value of type
bit[n], or the target of aletstatement aliasing classical bits - a value of type
array[<scalar>, n](one-dimensional)
and adds: "It is valid to use an indexing expression (e.g. my_array[1:3]) to arrive at one of
the types given above."
pyqasm implements only the first two. Any identifier or index expression as the iterable is
rejected.
Example QASM failure
Iterating a bit register:
OPENQASM 3.0;
bit[4] b = "1010";
for bit x in b { }
// ValidationError: Unexpected type <class 'openqasm3.ast.Identifier'> of set_declaration in loop.
Iterating an array:
OPENQASM 3.0;
array[int[8], 3] a = {1, 2, 3};
for int[8] i in a { }
// ValidationError: Unexpected type <class 'openqasm3.ast.Identifier'> of set_declaration in loop.
Iterating an index expression:
OPENQASM 3.0;
array[int[8], 4] a = {1, 2, 3, 4};
for int[8] i in a[1:2] { }
// ValidationError: Unexpected type <class 'openqasm3.ast.IndexExpression'> of set_declaration in loop.
Iterating a classical alias:
OPENQASM 3.0;
bit[4] b;
let c = b;
for bit x in c { }
// ValidationError: Qubit register b not found for aliasing
Change Requested
Extend the loop's iterable resolution to accept, in addition to the existing set and range
forms:
- An
Identifiernaming abit[n]— loop variable typebit, iterating index0..n-1. - An
Identifiernaming a one-dimensionalarray[<scalar>, n]— loop variable type
<scalar>, promoted to the declared loop variable type. - An
Identifiernaming a classical alias. - An
IndexExpressionthat evaluates to any of the above.
Two spec rules to enforce while doing so:
- Iteration order is guaranteed sequential by index:
iden[0], theniden[1], and so on. - Assigning to the loop variable inside the body must not modify the underlying array element.
A multi-dimensional array as the iterable must raise a ValidationError — the spec restricts
this to one-dimensional arrays.
Implementation Details
- The rejection is in
Qasm3Visitor._visit_forin_loopatsrc/pyqasm/visitor.py:2462. It
branches on the concrete type ofstatement.set_declarationand falls through for anything
that is not aDiscreteSetorRangeDefinition. - Factor the branch into a helper that returns a plain Python list of values to iterate. That
isolates the new cases and keeps the unrolling loop below unchanged. - Since the loop body is unrolled per value, the "assignment to the loop variable does not
write back" rule falls out naturally from binding a copy into the loop scope each
iteration — but add an explicit test, since it is easy to regress with a by-reference bind. - Depends on the
bit[n]representation work for case 1 and on the classical-alias work for
case 3; case 2 (arrays) is independent and could land first. - Tests:
tests/qasm3/test_loop.py— one case per iterable form, an index-expression iterable,
a write to the loop variable asserting the source array is unchanged, and a
multi-dimensional array asserting a cleanValidationError.
- 主要语言
- Python
- 星标
- 29
- 派生
- 33
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 15
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
qBraid/pyqasm 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
enhancement error-handling program-validation
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
Move the QASM 2 printer and its branch pre-processing out of qasm2.py可能已有人在做 @danielgaskins 于 10 天前认领。 未关闭enhancement qasm2
难度 4/5 3-5 天 新手友好度 22/100
维护者通常 1 天内回复
-
[BUG] dumps() emits extern calls without a semicolon, producing unparsable QASM可能已有人在做 @Jah-yee 于 18 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 25/100
维护者通常 1 天内回复
-
Parse failures raise ValidationError with an empty message; the ANTLR diagnostic is lost可能已有人在做 @tonycoder-hub 于 12 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 22/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
iceboundrock/AutoForge#304 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
fossasia/visdom-dev#77 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
aws-cloudformation/cfn-lint#4890 ·
维护者通常 2 天内回复