4 ms·
I have to agree with x.f(y).g(z) vs g(f(x,y),z)...jquery or d3.js would be terribly obtuse with the latter only. But there are times when the functional notati
by noobermin 11y ago
I have to agree with x.f(y).g(z) vs g(f(x,y),z)...jquery or d3.js would be terribly obtuse with the latter only.
But there are times when the functional notation is nicer than the OOish style. Really, having "both" is the right answer for libraries, although it might not always be possible. I suppose this proposal makes it easier for libs to do "both".
Also, can someone clarify for me, even though he mentions multimethods, these aren't really multimethods, right? Since f(x,y) becomes x.f(y), I'm assuming there is polymorphism involving the runtime type of x, but not y too, or is C++ getting true blue runtime multimethods?