Skip to content
Snippets Groups Projects
Commit 59cb44a3 authored by Joachim Breitner's avatar Joachim Breitner
Browse files

Explain why TcAxiomInstCo carries [TcCoercion], and not [TcType]

parent da66a8df
No related branches found
No related tags found
No related merge requests found
...@@ -90,6 +90,12 @@ differences ...@@ -90,6 +90,12 @@ differences
- TcSubCo is not applied as deep as done with mkSubCo - TcSubCo is not applied as deep as done with mkSubCo
Reason: they'll get established when we desugar to Coercion Reason: they'll get established when we desugar to Coercion
* TcAxiomInstCo has a [TcCoercion] parameter, and not a [Type] parameter.
This differs from the formalism, but corresponds to AxiomInstCo (see
[Coercion axioms applied to coercions]).
Why can't we use [TcType] here, in code not relevant for the simplifier?
Because of coercionToTcCoercion.
\begin{code} \begin{code}
data TcCoercion data TcCoercion
= TcRefl Role TcType = TcRefl Role TcType
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment