Hello, I try to work my way through "Type Parameters Proposal" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md). With my speed, I maybe and reading this very well written document before type parameters will be implemented in Go. xD Jokes aside, when I read it I found few sentences that sounds odd to me. Maybe some good soul would explain to me, am I right, or this is my bad, not good English?
At the beginning of the section (?) "Using a constraint" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#using-a-constraint) there is sentence "As shown above, constraints appear in the type parameter list as the meta-type of a type parameter." But I think that is should read "shown below". In the second paragraph (?) of the section "Operations based on type sets" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#operations-based-on-type-sets) we read "For special purpose operators like range loops, we permit their use of the type parameter has a structural constraint". Meaning of it is clear to me (at least it is), but it sound odd when I read it. Maybe is should be something like "the type parameter that has a structural constraint"? At the end totally pedantic hair splitting. At the end of the "Type sets" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md#type-sets) we have code snippet "interface{ E1; E2}". I feel that more consistent with the rest of the code would be with one more space: "interface{ E1; E2 }". Best, Kamil -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/de7fe316-ce69-48cd-8684-1c500cd058f6n%40googlegroups.com.
