On Mar 22, 2014, at 4:15 AM, Romain Manni-Bucau wrote:
> removed after and replaced all the boilerplate we added with
> AfterEvent.
Love it. Looks very elegant. Added a BeforeEvent to round it out.
Have some ideas to optimize. Ideally before/after could be zero cost unless
there are actua
Ok,
removed after and replaced all the boilerplate we added with AfterEvent.
Side note: i kept two passes with Invocation for fireEvent impl cause
I think it can be useful but today it is not so we can revert too if
you think it should
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannib
Thought the same but when you hack in arquilluan stack you realize it us
inefficient to understand the code. Your last commit proove it too:
Firer(afterxxx)
Fire(afterxx)
So we need a
Fire(afterx)
Makes code dumb to read and no more contextual so harder to follow.
Can you change st
