On Fri, Mar 29, 2013 at 11:49 AM, Chris Prather <ch...@prather.org> wrote:
> On Fri, Mar 29, 2013 at 2:44 PM, Chris Weyl <cw...@alumni.drew.edu> wrote:
> > To clarify here: "Aliasing allows me to trivially shunt one method aside
> > and create a new one in its place *while still being able to use the
> > previous method* w/o having to resort to method modifiers."
>
> To quote doy when I brought up this same point (with an entirely
> different phrasing) in this same thread:
>
> >
> > In that sense, there's no reason that this should be a role-specific
> > feature, and that's why MooseX::Aliases exists to begin with.
>
The existence of a MX module that can serve the same functionality is not,
in and of itself, a reason to drop core functionality. If that were the
case, then we should never have included MX::AttributeHandlers in core.
I'm still not seeing any compelling reason to drop excludes/alias. Am I
missing something here, like is the existence of alias/excludes in core
blocking Some Thing Good, or encouraging Very Bad Behaviour?
-Chris
--
Chris Weyl
Ex astris scientia
