21:44:32aethNot ideal, since it would also not override any internal function usage if it's just a layer on top of the functions... unless the methods use each other.
21:49:29aethWell, this would more be about defining two public APIs, where everything exported has two versions. So e.g. the method foobar* calls the function foobar. Perhaps with some of the methods going deeper so there are some interactions that can be overriden.
21:49:53aethInterestingly, there is a convention for a low-level %foobar variant of foobar, but not a convention for a high-level variant of foobar!
22:23:58pjbaeth: it is sufficient to declare those functions as notinline, so that the user may substitute it with advices.
22:24:17pjbaeth: so zero-cost to the general public, and cheap on the user who wants it.
0:13:15aethI love how they retconned <b> to be "Bring attention to" instead of "Bold"