in reply to Re^2: sort +*, @array
in thread sort +*, @array

but it's a direct equivalent

By that logic, every sort could be called a ST. That just doesn't make sense. Use the term as it is defined and well known: decorate-sort-undecorate!

retains the ST's generality

I don't see how it does that at all. Unless it can do decorate-sort-undecorate, it falls very far short of the ST's generality.

And it's not just about the "decorate" step, which your "key extractor" closure is roughly equivalent of. Because the ST has an explicit sort block (normally, unless it's the GRT variant :-)), it allows to execute arbitrarily complex Perl code in the comparison. Where does one do that in this Perl 6 "equivalent"?

I reckon we are the only monastery ever to have a dungeon stuffed with 16,000 zombies.

Replies are listed 'Best First'.
Re^4: sort +*, @array
by raiph (Deacon) on Dec 10, 2013 at 07:24 UTC
    I'm not saying that the design of the P6 builtin is ST, just that it is functionally equivalent, and even more concise.

    And it's not just about the "decorate" step, which your "key extractor" closure is roughly equivalent of.

    One critical point: while a "key extractor" closure is indeed roughly equivalent to the decorate step in terms of the role it's playing, it's multiple key extractor closures that is basically fully equivalent to the before map.

    Because the ST has an explicit sort block (normally, unless it's the GRT variant :-)), it allows to execute arbitrarily complex Perl code in the comparison. Where does one do that in this Perl 6 "equivalent"?

    You just specify a comparator closure (or multiple, if you want).

    (P6 can tell the difference due to a closure's number of args. If it has one, it's a key extractor closure, if it has two it's a comparator closure.)

    For lots more examples which are still correct modulo a few minor syntax shifts, see "The Sort Problem: a definitive ruling" from 2004.

    Which got me to focus on the Pair variant which maybe helps clarify the connection for you:

    sort { #`( key extractor closure) } => { #`( comparator closure) }, { #`( key extractor closure) } => { #`( comparator closure) }, ... @array

      I'm not saying your posts are full of blowhard marketing nonsense, but they're functionally equivalent. Do you even program, bro?