From d7ad1b5d552fa2cd8f85d9b4d8a2dcb1f9cfdd59 Mon Sep 17 00:00:00 2001 From: Aaron Weiss Date: Wed, 14 Sep 2022 10:43:29 -0700 Subject: [PATCH] Remove duplicate clause caught in rereading --- rfcs/generic-function-subtyping.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/rfcs/generic-function-subtyping.md b/rfcs/generic-function-subtyping.md index 0be0c3af..b9c0c430 100644 --- a/rfcs/generic-function-subtyping.md +++ b/rfcs/generic-function-subtyping.md @@ -119,10 +119,8 @@ parameters, it doesn't make sense to warn on their instantiation (as illustrated by the example of actually applying `f` to some particular data in the definition of `rank2`), but it's still just as problematic if we were to accept instantiated functions at polymorphic types. Thus, it's important that we -actually ensure that we only instantiate in covariant contexts, but it's still -just as problematic if we were to accept instantiated functions at polymorphic -types. So, we must ensure that subtyping only instantiates in covariant -contexts. +actually ensure that we only instantiate in covariant contexts. So, we must +ensure that subtyping only instantiates in covariant contexts. It may also be helpful to consider an example of rank-1 polymorphism to understand the full scope of the behavior. So, we can look at what happens if we