You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment our concrete syntax is highly coupled to the syntax we use for type checking and our proofs. It might make sense to separate these to allow for cleaner proofs and type checking, and allow us to add new features without altering the core language too much.
For example, PADS/ML has DDC:
The tricky thing is doing this in such a way that preserves good error messages (see #2).
The text was updated successfully, but these errors were encountered:
One idea to get around the error reporting problem is to do what GHC does: implement a type checker+inference on the complex AST and a simple, more elegant type checker on the fully explicit core representation as a sanity check for debugging purposes.
Could be as close to a direct port of the typechecker in the formal specification, perhaps, seeing as that would have progress, preservation, and soundness already verified:
At the moment our concrete syntax is highly coupled to the syntax we use for type checking and our proofs. It might make sense to separate these to allow for cleaner proofs and type checking, and allow us to add new features without altering the core language too much.
For example, PADS/ML has DDC:
The tricky thing is doing this in such a way that preserves good error messages (see #2).
The text was updated successfully, but these errors were encountered: