Probably erasure, but that wasn't Odersky's fault either. He was tasked with building a prototype Java source compiler, with no help from the VM team, that could handle generics. He did so, without using any Sun source, as far as I know, and that later became javac 1.3, which apparently had generics, but disabled by default. They were removed in 1.4, then readded with a slew of extra problems in 1.5.
If he had had some help from the VM team, he could have considered a C#-like implementation. In any case, the final decision was Sun's, and though I disagree with parts of it (wildcards, adding 1000s of warnings to already-existing code, releasing it before their *own* code was warning-free), it really isn't as bad as it can seem if you look mainly at the corner cases. On Thu, Jun 23, 2011 at 1:27 PM, Casper Bang <[email protected]> wrote: > > I'm no conspiracy theorist but... > > Are you thinking of wildcards? If so, in all fairness, that was > primarily a brainchild of Mads Torgersen I believe (now working with > Neal Gafter on C# which uses definition-site variance rather than use- > site variance). > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
