From a181ade6400bee073b7683b2ced631d8d65f847d Mon Sep 17 00:00:00 2001 From: Ian Lance Taylor Date: Fri, 10 Sep 2021 10:07:39 -0700 Subject: design/43651-type-parameters: minor formatting/wording fixes Change-Id: I94003ba5f108076abf85786374ee9d537353683c Reviewed-on: https://go-review.googlesource.com/c/proposal/+/349069 Trust: Ian Lance Taylor Reviewed-by: Ian Lance Taylor --- design/43651-type-parameters.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/design/43651-type-parameters.md b/design/43651-type-parameters.md index 341124e..77e9b43 100644 --- a/design/43651-type-parameters.md +++ b/design/43651-type-parameters.md @@ -714,7 +714,7 @@ That is exactly the type set of `interface{ M1; M2 }`. The same applies to embedded interface types. For any two interface types `E1` and `E2`, the type set of `interface{ -E1; E2}` is the intersection of the type sets of `E1` and `E2`. +E1; E2 }` is the intersection of the type sets of `E1` and `E2`. Therefore, the type set of an interface type is the intersection of the type sets of the element of the interface. @@ -887,7 +887,7 @@ type parameter in any way that is permitted by every member of the type set of the parameter's constraint. This applies to operators like '<' or '+' or other general operators. For special purpose operators like `range` loops, we permit their use -of the type parameter has a structural constraint, as [defined +if the type parameter has a structural constraint, as [defined later](#Constraint-type-inference); the definition here is basically that the constraint has a single underlying type. If the function can be compiled successfully using each type in the -- cgit v1.3