aboutsummaryrefslogtreecommitdiff
path: root/lib/std/Thread
diff options
context:
space:
mode:
authormlugg <mlugg@mlugg.co.uk>2023-10-24 04:36:35 +0100
committermlugg <mlugg@mlugg.co.uk>2023-10-24 14:28:33 +0100
commit20bb81166f36668413703e0d74b3e283c55ab8ca (patch)
treed68649f59e0899fbc49e7f9a188d3738f0ca1a3f /lib/std/Thread
parentbb0419599aa93455f3ae0969f4bfd80204807596 (diff)
downloadzig-20bb81166f36668413703e0d74b3e283c55ab8ca.tar.gz
zig-20bb81166f36668413703e0d74b3e283c55ab8ca.zip
InternPool: remove runtime_value representation
The main goal of this commit is to remove the `runtime_value` field from `InternPool.Key` (and its associated representation), but there are a few dominos. Specifically, this mostly eliminates the "maybe runtime" concept from value resolution in Sema: so some resolution functions like `resolveMaybeUndefValAllowVariablesMaybeRuntime` are gone. This required a small change to struct/union/array initializers, to no longer use `runtime_value` if a field was a `variable` - I'm not convinced this case was even reachable, as `variable` should only ever exist as the trivial value of a global runtime `var` decl. Now, the only case in which a `Sema.resolveMaybeUndefVal`-esque function can return the `variable` key is `resolveMaybeUndefValAllowVariables`, which is directly called from `Sema.resolveInstValueAllowVariables` (previously `Sema.resolveInstValue`), which is only used for resolving the value of a Decl from `Module.semaDecl`. While changing these functions, I also slightly reordered and restructured some of them, and updated their doc comments.
Diffstat (limited to 'lib/std/Thread')
0 files changed, 0 insertions, 0 deletions