On Tue, Jan 19, 2021 at 4:36 AM Kevin Chadwick <m8il1i...@gmail.com> wrote:
>
> On 1/19/21 12:21 PM, Axel Wagner wrote:
> > And, of course, you can change the suggested syntax again. But every time
> > you do
> > a change like that, you are flushing the entire previous discussion down the
> > drain, because we now have to re-consider all aspects of the design, from
> > tokenization, over parsing to type-checking and implementation etc.
>
> OK, but using a T all over the place, sucks.
Note that that's just a stylistic convention. We've gone back and
forth on that convention even while keeping the rest of the syntax the
same.
Basically, in a design like the current issue 43651 proposal, type
parameters have a name. What should that name be? We've currently
settled on names like "T". But they could just as well be names like
"element" or "number". The proposal permits writing code like
func Find[element comparable](s []element, val element) int {
...
}
func Min[number constraints.Ordered](a, b number) number {
...
}
Ian
--
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/CAOyqgcVQ6TtqLX5OG4A%2BdEG0oJvJF-uKwFAgv%2Bqdpw8Oq-nDBQ%40mail.gmail.com.
