Matthew Lutze
Matthew Lutze
I would give them names like TypeErrorForThisParticularCase but I don't have a strong opinion other than that it ought to be centralized.
Ok, I retract my opposition.
You can treat Provenance.Match as going in both/either direction. The point is at the end you have a path.
I think the minutiae are still being debated... but one of the great forces will give up soon.
The constraints form a kind of big graph, where effects and effect variables are nodes. Effect *sources* are where effects are produced --- this happens when we call an effect...
> @JonathanStarup @mlutze Does this sparkle with the boys? Does it bring joy. > > This is based on the Rust design I'm OK with this though it breaks the...
Keep it open in case we get distracted by something and don't fix it :P
For ApplyDef, you'll need to extract it from the signature. `defn.spec.eff` contains an effect you can use.
That sounds about right to me.
Can you share the input program and stack trace?