<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 18 May 2017, at 11:05, Didier Verna <<a href="mailto:didier@lrde.epita.fr" class="">didier@lrde.epita.fr</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Pascal Costanza wrote:<br class=""><br class=""><blockquote type="cite" class="">I’m just guessing, but one reason I can think of is that almost all of<br class="">the built-in method combinations (except for standard and progn) are<br class="">applicative. before/after methods don’t have a direct impact on the<br class="">return value of a generic function call, so their primary purpose is<br class="">to allow for specifying side effects, which presumably doesn’t make a<br class="">lot of sense for applicative combinators.<br class=""><br class="">Does that make any sense?<br class=""></blockquote><br class=""> Hmmm. Nope :-) </div></div></blockquote><br class=""></div><div>Darn. :-)</div><div><br class=""></div><div class="">
<span style="font-family: Menlo-Regular; font-size: 11px;" class="">--</span><br style="font-family: Menlo-Regular; font-size: 11px;" class=""><span style="font-family: Menlo-Regular; font-size: 11px;" class="">Pascal Costanza</span><br style="font-family: Menlo-Regular; font-size: 11px;" class=""><br class="">
</div>
<br class=""></body></html>