So, on my wishlist:

  1. Only export methods this the trait promises to provide
  2. Conflict resolution via method renaming
  3. Conflict resolution via denying a method (so another trait can provide it)
  4. Trait requirements must be explicitly met or we fail at compile time
  5. Properly respecting the above traits even when aggregating traits into a new trait

With the exception of the first item on that list, Class::Trait handles this. Does Perl6::Roles handle these? If so, I'll consider a switch.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^6: Detecting an imported function by Ovid
in thread Detecting an imported function 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.