Hacker News new | past | comments | ask | show | jobs | submit login

Aside from backwards compatibility, what's good about type erasure for generics?



It permits languages on the platform with substantially-richer compile-time type systems than the primary language on the platform with good interior stories (this was, IIRC, a substantial problem with Scala.NET.)


Doing it a better way is hard


Is it, though? The most basic implementation, where things are still erased at runtime by the JIT, should be fairly simple, although it will not give the expected perf gains, of course.

Either way, CLR and C# did it a long time ago, and in the same time period when Java acquired its type-erased generics.


They care too much about backwards compatibility I think. .NET had done generics this way from the beginning.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: