On Thu, 10 Apr 2014, Chris Weyl wrote:
On Wed, Apr 9, 2014 at 11:33 PM, Niall Young <ni...@iinet.net.au> wrote:
If we had Traits, with explicit conflict resolution in a matrix of slots
at instance
construction, then there's a much more useful 'abstract base class' than
jumping
through any consumption-order hoops, imho.
This statement looks interesting, but I'm not entirely sure what you mean.
Would the
functionality provided by MooseX::Traits or MooseX::Traitor be substantially
equivalent to what
you're talking about?
Both look interesting, but at a glance - no, what I'm referring to is:
http://www.cs.cmu.edu/~aldrich/courses/819/Scha03aTraits.pdf
being commutative and associative, all flattened into the consuming class in 1
pass, with explicit conflict resolution and the resulting class may be concrete
or abstract (not all requirements have been met, so cannot instantiate).
--
Niall Young
ni...@iinet.net.au
