Re:How C++ Resolves a Function Call
by yvdriess on Tuesday March 16, 2021 @06:51AM
(#26475108)
It's one of those things where on rare occasion where it's applicable it really simplifies the code. Kind of like dynamically scoped variables.
It's been a while that I've hacked CL, but I remember method combinators being used in mixin-style programming[1].
A call-next-method is a simplification tool in that context, and it doesn't hard-couple your generic functions.
With concepts now in C++, I wouldn't be surprised to see a resurgence of template-mixins, and there it really helps to have some introspection into the partial ordering.
It's been a while that I've hacked CL, but I remember method combinators being used in mixin-style programming[1]. A call-next-method is a simplification tool in that context, and it doesn't hard-couple your generic functions. With concepts now in C++, I wouldn't be surprised to see a resurgence of template-mixins, and there it really helps to have some introspection into the partial ordering.
[1] That is, Flavors mixins, not dlang mixins ;)