3 ms·
> Probably rejected willingly even ('where are my objects?') Local type inference was rejected in Java in 2001 because "you need to spec your types precisely"
by dmitriid 8y ago
> Probably rejected willingly even ('where are my objects?')
Local type inference was rejected in Java in 2001 because "you need to spec your types precisely"
- agumonkey 8y agois it published online ?
- TuringTest 8y agoIIRC it was common knowledge, as it was an "obvious improvement" over C-style undeclared variables. Have in mind that type inference applied only to local values, not propagated globally through the code structure as in ML.
- dmitriid 8y agoFound it here: https://stackify.com/whats-new-in-java-10/ https://stackify.com/whats-new-in-java-10/ ——— start quote ——— This feature has been a long time coming. It was suggested as far back as 2001, and was closed at that time with the following comment by Gilad Bracha: Humans benefit from the redundancy of the type declaration in two ways. First, the redundant type serves as valuable documentation – readers do not have to search for the declaration of getMap() to find out what type it returns. Second, the redundancy allows the programmer to declare the intended type, and thereby benefit from a cross-check performed by the compiler. ——— end quote ——— Link to original RFE and quote source: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4459053 https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4459053
- agumonkey 8y agoInteresting, I kinda agree about the need for redundancy at times (which is not forbidden by ML typing). But it rejected a very good idea for a decade.. A bit like lambda expressions. Damn Java