With our new IRCEventHandler UDA scheme, there was a lot of manual boilerplate involved in defining the various methods; .onEvent, .channelPolicy, .chainable and so forth. But they really only did two things; take the passed value and save it somewhere else, then return this by reference.
IRCEventHandler.Regex.expression is an exception in that it not only saves the passed expression, but also instantiates the regex engine. So it was left as-was.
With our new
IRCEventHandler
UDA scheme, there was a lot of manual boilerplate involved in defining the various methods;.onEvent
,.channelPolicy
,.chainable
and so forth. But they really only did two things; take the passed value and save it somewhere else, then returnthis
by reference.Now it's done with a mixin template
Wrap
that automatically generates them.Compilation memory went up some, but marginally.
IRCEventHandler.Regex.expression
is an exception in that it not only saves the passed expression, but also instantiates the regex engine. So it was left as-was.