I'd encourage you to upload it to CPAN. The module collection is large and diverse enough that additional dilution or "glut" seems like a misplaced concern.

Particularly in interesting areas like this where there's active ongoing discussion and consideration, I think it's helpful to have a handful of different implementations available that people can put through their real-world paces... And looking at different takes on a similar problem can help to clarify some of the core commonalities and separate out various useful idioms.

In response to the questions in the OP, no, I haven't yet used a traits-based system, but I have spent a bunch of time hacking different types of method aggregation, generation, and composition techniques in Perl, so yes, I would be interested in seeing how or if traits would help me address some of the same concerns.

It would be very helpful to have a more realistic example that both synopsized the Class::Trait interface and also demonstrated how such traits can be useful... I haven't yet been able to visualize a compelling example case, but I'll give it some more thought.

In reply to Re: Class::Trait to the CPAN? by simonm
in thread Class::Trait to the CPAN? by Ovid

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.