On 18 May 2017, at 11:05, Didier Verna <didier@lrde.epita.fr> wrote:

Pascal Costanza wrote:

I’m just guessing, but one reason I can think of is that almost all of
the built-in method combinations (except for standard and progn) are
applicative. before/after methods don’t have a direct impact on the
return value of a generic function call, so their primary purpose is
to allow for specifying side effects, which presumably doesn’t make a
lot of sense for applicative combinators.

Does that make any sense?

 Hmmm. Nope :-)