Hi Paul, I tend to agree with you since I don't like the Map extension too, the only concern is just to understand how strict backward compatibility we want to keep, or if we want almost "redesign" the public APIs. It is an important choose we have to made in a VOTE, I suggest to promote first the branch in trunk and then understanding if breaking the compatibility or not. Thanks for your hints, much more than appreciated! Have a nice day, all the best! Simo
http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Mon, Sep 5, 2011 at 5:54 AM, Paul Benedict <[email protected]> wrote: > I want to get rid of it extending map. Have it define as asMap() > function instead. Especially since JDK 8 is bringing in extension > methods, which adds new (and default) methods to all collections, it > won't look very nice. Let's make a break now. > > On Sun, Sep 4, 2011 at 9:20 PM, Raman Gupta <[email protected]> wrote: >> On 09/04/2011 04:00 PM, James Carman wrote: >>> On Sun, Sep 4, 2011 at 3:44 PM, Simone Tripodi <[email protected]> >>> wrote: >>>> >>>> That is able to 'auto-cast' the retrieved object while Map#get() not. >>>> >>> >>> I believe the feature is actually called "type inference", not "auto-cast." >>> :) >> >> Thanks for the explanation... I see now that via the generic method >> the compiler infers the return type from the assignment type. >> >> Cheers, >> Raman >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
