[ASDAlexander77]

Nodes the compiler builds with NodeFactory have no position, so an error inside one was reported at 1:1 of the file:

function main() {
    const n = 5;
    for (const x of n) {}   // was 1:1, now 3:5: Can't resolve property 'length' of type s32
    using r = 5;            // was 1:1, now 4:11: Can't resolve property 'dispose' of type s32
}

Found for for...of, for...in, for await, yield*, a class [Symbol.iterator], using and await using. #541 and #557 fixed the generated cast, field initializers and the implicit constructor one site at a time (stamping pos). This fixes the rest in one place:

• mlirGen(Statement) records where the statement is, as a location without the debug scope (generatedNodesAnchor). A statement the compiler made itself (no position) keeps the anchor of the one it was made for.
• loc() gives a node with no position (isTextRangeEmpty()) that anchor, fused with the current overwriteLoc and debug scope. Nodes with a position are unchanged.
• The dispose call is built at the scope's exit; mlirGenDisposeOne anchors it at the using declaration.

The anchor holds no debug scope, so a node is never given a scope from another function: --di JIT and --di --emit=obj of loops, using and yield* were checked.

Tests: diagnostic-location/for_of.ts, for_in.ts, using.ts, error text with line and column, failing on any :1: position. The existing three diagnostic-location tests still pass.

Full Release suite: 4092/4092 passed.

🤖 Generated with Claude Code