4 ms·

Java has generics and overloading; how far can you realistically get before building a full frontend? Honest question.

• saagarjha 7y ago
  Anecdotal, but I’ve found it difficult to find a Java autocomplete plug-in that doesn’t run Eclipse in the background to work.
• username90 7y ago
  Java generics are just syntactic sugar for Object, so not a problem at all since you can't do anything with them. Java overloading is simple since all functions are in the same file (so doesn't change overload behavior depending on which files are imported) and Java lacks the user type casts C++ has, so just pick the signature fitting all provided values (with numeric casts) or throw.
  • josefx 7y ago
    > Java generics are just syntactic sugar for Object, Only if you do not have a concrete boundary in the generic declaration, T extends Foo can result in a function definition that takes a Foo instead of an Object. > Java overloading is simple since all functions are in the same file (so doesn't change overload behavior depending on which files are imported) import static java.lang.Math.*; for programmers too lazy to write Math.sin instead of sin.
• lallysingh 7y ago
  The grammar is still context free.