6 ms·

C++ and Rust require extra disambiguating syntax in some contexts (C++ the `foo.template bar<T>()` syntax, Rust the "superfish operator" `foo.bar::<T>()`. Java

C++ and Rust require extra disambiguating syntax in some contexts (C++ the `foo.template bar<T>()` syntax, Rust the "superfish operator" `foo.bar::<T>()`. Java works around the problem by awkwardly putting the generic argument list in front of the method name (`foo.<T>bar()`). I don't know about C#.

steveklabnik 6y ago
(teeny tiny note: turbofish, not superfish)
- Sharlin 6y ago
  Oops :D
DougBTX 6y ago
C# is `foo.bar<T>()`, I’m not sure what compromises that had to make for that to work but from an end-user perspective it works well.
- oxnrtr 6y ago
  They parse it one way, and if they figure out the other parse option was right, they go back and fix the parse tree. Basically, unlimited look-ahead.
  - lostmsu 6y ago
    Is it somehow a problem?
oxnrtr 6y ago
Using [] is the optimal choice for languages in general, but they can't even use that because they blew away that syntax for indexing.
- Sharlin 6y ago
  Scala uses [] for generics and () for indexing, which sort of makes sense given that in the end arrays are just functions.
  - lostmsu 6y ago
    So are the uninstantiated generic types ;-)