diff options
| -rw-r--r-- | compiler/typecheck/TcInstDcls.hs | 2 | ||||
| -rw-r--r-- | docs/users_guide/glasgow_exts.xml | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/compiler/typecheck/TcInstDcls.hs b/compiler/typecheck/TcInstDcls.hs index 9b07554a45..5ee64791e9 100644 --- a/compiler/typecheck/TcInstDcls.hs +++ b/compiler/typecheck/TcInstDcls.hs @@ -973,7 +973,7 @@ Notice that This is a bit of a hack, but works very nicely in practice. - * Note that if a method has a locally-polymorhic binding, there will + * Note that if a method has a locally-polymorphic binding, there will be yet another implication for that, generated by tcPolyCheck in tcMethodBody. E.g. class C a where diff --git a/docs/users_guide/glasgow_exts.xml b/docs/users_guide/glasgow_exts.xml index 7bb2f68e95..edfdc849bf 100644 --- a/docs/users_guide/glasgow_exts.xml +++ b/docs/users_guide/glasgow_exts.xml @@ -6679,8 +6679,8 @@ level of the signature for <literal>f1</literal>. But in the case of of <literal>f2</literal> we give a kind annotation in the <literal>forall (a:k)</literal> binding, and GHC therefore puts the kind <literal>forall</literal> right there too. This design decision makes default case (<literal>f1</literal>) -as polymorphic as possible; remember that a <emphasis>more</emphasis> polymorhic argument type (as in <literal>f2</literal> -makes the overall function <emphasis>less</emphasis> polymorphic, because there are fewer accepable arguments. +as polymorphic as possible; remember that a <emphasis>more</emphasis> polymorphic argument type (as in <literal>f2</literal> +makes the overall function <emphasis>less</emphasis> polymorphic, because there are fewer acceptable arguments. </para></listitem> </itemizedlist> </para> |