News for hackers. Stuff that matters.
Re:Go generics may use square brackets [] not parenthesis () by hu3 on Tuesday July 14, 2020 @10:39PM (#23840603)
You can't please everyone. So might as well pick the most common keyboard layout among your users and call it typical computer keyboard.

I'm afraid there's no easy solution to this problem but I'd like to hear your suggestion.

Re:Go generics may use square brackets [] not parenthesis () by whatshisface on Tuesday July 14, 2020 @10:45PM (#23840640)
Well, there's always

   begin
and

   end

Isn't there? ;)
Re:Go generics may use square brackets [] not parenthesis () by deathanatos on Wednesday July 15, 2020 @12:43AM (#23841408)
Or… indentation! crowd gasps; lightning flashes; thunder claps; maniacal laughter is heard in the distance
Re:Go generics may use square brackets [] not parenthesis () by hu3 on Wednesday July 15, 2020 @07:45AM (#23843842)
generics with begin and end?
Re:Go generics may use square brackets [] not parenthesis () by asa4akj on Wednesday July 15, 2020 @09:03AM (#23844566)
Well, Haskell uses just a space.
Re:Go generics may use square brackets [] not parenthesis () by riffraff on Wednesday July 15, 2020 @08:18AM (#23844121)
I think Ada does something like that (type T is array of I with E) but yeah, I wouldn't advocate that :)
Re:Go generics may use square brackets [] not parenthesis () by _ph_ on Wednesday July 15, 2020 @10:17AM (#23845520)
There is no easy solution to the problem, so no one should pretend there is. Yes, if I program in Go, I have to type square brackets [] from time to time for slices. But for me it is more painful, so I strongly prefer the generics notation with parens ().

It may be, that in the end the parens are the solution to use, but at least it should be considered in the discusion, that they are not very easy to use for a lot of non-English layouts. Just assuming anyone in the world would use an English layout, is quite offensive in my eyes.