You've overlooked ~|> or ~> or whatever that operates on context by
default.
given @foo {
~> classify ~> @categories;
~> sort -> @sorted_foo;
~> improve ~> @bar;
};
Personally, I'd like to see that syntax improved a little.
Anyway, I'd suggest that the order of execution of lines beginning with
a dangling grin or dragon operator by undefined. (So that p6.1 can run
them in separate threads.)
Which makes for a good motorized personal transporter(*) into another
TFH(+): Threads.
(!)
=Austin
(*) Segway -- aka segue.
(+) Topic From Hell
(!) All your base are belong to us! Fnord!
--- Michael Lazzaro <[EMAIL PROTECTED]> wrote:
>
> So, to bring this thread back on track *again*, I hopefully offer
> this
> summary.
>
>
> 1) Damian's idea of using ~> and <~ as L2R and R2L is well-liked.
> Thus:
>
> @out = grep { ... } map { ... } @in; # (1) (perl5)
>
> becomes any of the following:
>
> @out = grep { ... } <~ map { ... } <~ @in; # (2) (perl6)
>
> @out <~ grep { ... } <~ map { ... } <~ @in; # (3)
>
> @in ~> map { ... } ~> grep { ... } ~> @out; # (4)
>
> My impression was that this was _instead_ of (1), eliminating the
> specialized syntax of the map, grep, etc. functions in favor of this
> more generic piping syntax, but that wasn't explicitly stated. Is
> that
> correct?
>
> 2) You might be able to combine L2R and R2L piping in one statement.
>
> Maybe.
>
> 3) How pretty you think the above is depends almost entirely on how
> the
> tilde is rendered in your font.
>
> 4) Some people like the idea of having Unicode operators in perl6.
> Some don't. There are issues with it. Larry hasn't come up with a
> ruling yet. We should wait for his decision.
>
> 5) Sarcasm is, apparently, dead.
>
> MikeL
>
