News for hackers. Stuff that matters.
Re:Carbon Language: An experimental successor to C++ by xigoi on Tuesday July 19, 2022 @03:23PM (#32156648)
I can't handle <> syntax for generics. It's impossible to auto-pair and looks ugly.

The real solution is [] for generics and something else for indexing.

Re:Carbon Language: An experimental successor to C++ by wtetzner on Thursday July 21, 2022 @08:15PM (#32186933)
Using function call syntax for array indexing always made sense to me. Functions are mappings from inputs to outputs, and arrays are mappings from indexes to values.
Re:Carbon Language: An experimental successor to C++ by xigoi on Friday July 22, 2022 @04:26AM (#32189819)
I agree, but explain that to programmers who think parametric polymorphism is too complex.
Re:Carbon Language: An experimental successor to C++ by int_19h on Monday July 25, 2022 @03:07PM (#32229405)
Given that one of the languages that historically used the same syntax for array access and function invocation since day one is BASIC, I would dare say that it's not a complicated concept.
Re:Carbon Language: An experimental successor to C++ by renox on Wednesday July 20, 2022 @06:07AM (#32163571)
When looking for eleguant solutions: look at D, it's full of pearls: they use !() for generics.