Extension methods and API evolution
Paulo Levi
i30817 at gmail.com
Fri Dec 18 01:12:40 PST 2009
Very strange that you seem to value fragmentation over centralization. The
"useful" higher order functions have been explored for more than ten years
in languages like haskell, that have no problem with breaking compatibility.
Your solution would be what? Wait for 10 different Collections clones and
choose the "best" for each project?
I for one am tired of that.
As for traits, i believe that either extension methods should be in but
hidden, so traits could be implemented later, or traits come at the same
time as lambdas. Override-ability is key for the success of any additional
methods in the "interfaces".
More information about the lambda-dev
mailing list