Daniel P H Fox
Daniel P H Fox
Storing ancestry information also has the potential to significantly improve lifetime analysis, by allowing analysis to flow up to common ancestors rather than having to flow down from the scopes...
Proposed user facing API surface: ``` Contextual:is(value):inside(function(scope) -- ... end) ``` The returned `scope` is internally weakly mapped to `value`.
Alternatively, it'd be *possible* to ship a design that weakly maps the *current* scope to a value, but this is undesirable because it forces the developer to explicitly introduce scopes...
As a further consideration, `:now()` is not scope-aware. It would need to be given a scope to inspect. For this purpose, we could introduce a new `:here(scope)` accessor. Alternatively, we...
The mechanisms for `:during()/:now()` and `:inside()/:here()` should not be mixed or interact in any way. This would introduce asymmetry (where `:now()` is scope-unaware but `:here()` is call-stack-aware) and could confuse...
This is a known issue; should be fixed by #323
Fixed in `push-pull-execution` thanks to a reformulation of `springCoefficients`