roc/compiler/load_internal
Ayaz Hafiz aa9b70a7c8
Distinguish between pending and resolved ability stores
Now that we have unspecialized lambda sets, we need to properly copy
their specialization variables when a module imports another modules'
ability store. I think it will be easier to ensure the correctness if
we distinguish between a "pending" ability store (which may contain
imports whose variables have not been added to subs yet) and "resolved"
abilities stores, which are what we care about for solve and later on.

There is a cost to this since `PendingAbilitiesStore#resolve` destroys
and collects all of the ability member data, rather than in-place
mutating as we did before. However, the resulting `AbilitiesStore` is
now much smaller, so the memory footprint will be better, and also
every field besides `ability_members` will be moved rather than copied.
2022-06-09 12:52:40 -04:00
..
src Distinguish between pending and resolved ability stores 2022-06-09 12:52:40 -04:00
tests Instantiate unspecialized lambda sets under aliases and opaques 2022-06-07 14:41:42 -04:00
.gitignore Updated tests to use deterministic tmp dir 2022-04-20 21:25:12 -07:00
Cargo.toml cargo fix --edition 2022-05-16 17:04:17 +02:00