aboutsummaryrefslogtreecommitdiff
path: root/src/Module.zig
diff options
context:
space:
mode:
authormlugg <mlugg@mlugg.co.uk>2024-06-18 04:41:02 +0100
committermlugg <mlugg@mlugg.co.uk>2024-06-18 04:48:24 +0100
commit0486aa5081eee589edce79b721f35fadf2de1625 (patch)
tree6d27bacdf27943c6c2e0edbc24243dd7f0cf769b /src/Module.zig
parentedf14777bae56c3a6a155c59f793dc432656c1de (diff)
downloadzig-0486aa5081eee589edce79b721f35fadf2de1625.tar.gz
zig-0486aa5081eee589edce79b721f35fadf2de1625.zip
Zir: provide absolute node for `reify`
Since we track `reify` instructions across incremental updates, it is acceptable to treat it as the baseline for a relative source location. This turns out to be a good idea, since it makes it easy to define the source location for a reified type.
Diffstat (limited to 'src/Module.zig')
-rw-r--r--src/Module.zig1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/Module.zig b/src/Module.zig
index 31b022fd37..3faa1b8780 100644
--- a/src/Module.zig
+++ b/src/Module.zig
@@ -2374,6 +2374,7 @@ pub const LazySrcLoc = struct {
.union_decl => zir.extraData(Zir.Inst.UnionDecl, inst.data.extended.operand).data.src_node,
.enum_decl => zir.extraData(Zir.Inst.EnumDecl, inst.data.extended.operand).data.src_node,
.opaque_decl => zir.extraData(Zir.Inst.OpaqueDecl, inst.data.extended.operand).data.src_node,
+ .reify => zir.extraData(Zir.Inst.Reify, inst.data.extended.operand).data.node,
else => unreachable,
},
else => unreachable,