diff options
| author | mlugg <mlugg@mlugg.co.uk> | 2023-10-24 05:03:25 +0100 |
|---|---|---|
| committer | mlugg <mlugg@mlugg.co.uk> | 2023-10-24 14:28:34 +0100 |
| commit | 67caf685056bcdbbe4e696cada927615b0dd6fe9 (patch) | |
| tree | 2f715cabde6864720c4943e006cab600c3416e5d /lib/std/Thread/RwLock.zig | |
| parent | 7882bdcb7e1b012ff388c4abe0b57aa048bb2ce3 (diff) | |
| download | zig-67caf685056bcdbbe4e696cada927615b0dd6fe9.tar.gz zig-67caf685056bcdbbe4e696cada927615b0dd6fe9.zip | |
Sema: rename value resolution functions
Having simplified these functions in a previous commit, I felt inclined
to refactor their names, which were previously quite inconsistent. There
are now 4 "core" functions:
* `resolveValue` (previously `resolveMaybeUndefVal`) allows runtime-known and undef values.
* `resolveConstValue` (previously `resolveConstMaybeUndefVal`) allows undef but not runtime-known values.
* `resolveDefinedValue` (name unchanged) allows runtime-known values but not comptime-known undef.
* `resolveConstDefinedValue` (previously `resolveConstValue`) does not allow runtime-known or undef values.
You can see the inconsistencies in the old names here - sometimes we
specified "maybe undef", and sometimes we went the other way by
specifying "defined". With the new names, the most common function,
`resolveValue`, has the shortest name and does the most general thing,
and is the baseline that the other functions are adding logic to.
Some other functions were also renamed:
* `resolveMaybeUndefLazyVal` -> `resolveValueResolveLazy`
* `resolveMaybeUndefValIntable` -> `resolveValueIntable`
* `resolveMaybeUndefValAllowVariables` -> `resolveValueAllowVariables`
Diffstat (limited to 'lib/std/Thread/RwLock.zig')
0 files changed, 0 insertions, 0 deletions