So, in "Perl6" you would write a seven-line subroutine to define a custom operand, and *then* you could write: 

my %missing-words = %book-words - %dictionary;

[download]
Whereas in Perl you could use built-ins (avoiding potential errors, and taking advantage of low-level optimizations) and simply write: 
my %missing = map { $_ => 1 } grep { ! exists $dict{ $_ } } keys %book
+;

[download]
That's a great example of how not useful the butterfly's bells and whistles are *in real life.*

(Oh, and I see you showing off your 'hyphens-in-var-names' bell-and-whistle, but honestly, all that does is make the code less readable.)

Not impressed.


The way forward always starts with a minimal test.

In reply to Re^2: [Perl6] Can i put a operator in container (Perl 6) by 1nickt
in thread [Perl6] Can i put a operator in container by freakcoco

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.