diff options
| author | Andrew Kelley <andrew@ziglang.org> | 2022-02-27 16:51:33 -0700 |
|---|---|---|
| committer | Andrew Kelley <andrew@ziglang.org> | 2022-02-27 16:51:33 -0700 |
| commit | 9d4cfd9048d71d7519d759b9849914ce154d1877 (patch) | |
| tree | e28008bbb3ff86babf48fbe4b80d078e9217c2f3 /src/ThreadPool.zig | |
| parent | 71aa5084edd1d3fba5bf8db87c4cf0d03667a566 (diff) | |
| download | zig-9d4cfd9048d71d7519d759b9849914ce154d1877.tar.gz zig-9d4cfd9048d71d7519d759b9849914ce154d1877.zip | |
Sema: resolve necessary information ahead of time
Do the fallible logic in Sema where we have access to error reporting
mechanisms, rather than in Type/Value.
We can't just do the best guess when resolving queries of "is this type
comptime only?" or "what is the ABI alignment of this field?". The
result needs to be accurate. So we need to keep the assertions that the
data is available active, and instead compute the necessary information
before such functions get called.
Unfortunately we are stuck with two versions of such functions because
the various backends need to be able to ask such queries of Types and
Values while assuming the result has already been computed and validated
by Sema.
Diffstat (limited to 'src/ThreadPool.zig')
0 files changed, 0 insertions, 0 deletions
