News for hackers. Stuff that matters.

A comment on Go generics draft design: building a hashtable. Parent comment

Re:Go generics draft design: building a hashtable by tapirl on Wednesday June 17, 2020 @09:19PM (#23558785)
Comparing it with the builtin hashtable:

* the custom one: hashtable.Table(string, int)

* the builtin one: map[string]int

The syntax forms are quite different. Wouldn't it be better to make them consistent? Is it so hard to achieve this?

[ Parent | on HN ]
Re:Go generics draft design: building a hashtable by jeremyjh on Wednesday June 17, 2020 @09:43PM (#23558915)
It would not surprise me to learn that the parser has special rules for the token "map".
[ Parent | on HN ]
Re:Go generics draft design: building a hashtable by tapirl on Wednesday June 17, 2020 @10:13PM (#23559107)
Yes, the fact that "map" is a keyword and "Table" is not really makes a trouble for parser. But I think we should think towards the road. There should be always a solution.
[ Parent | on HN ]
Re:Go generics draft design: building a hashtable by mpfundstein on Thursday June 18, 2020 @04:53AM (#23561152)
lisp
[ Parent | on HN ]