[perl #127226] QUOTE does not remove backslash with adverb :b

On Fri, 23 Jun 2017 05:28:22 -0700, c...@zoffix.com wrote: > On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > > my $x = 42; say Q:s:b{\$x} > > > > # OUTPUT«\42␤» > > # EXPECTED«42␤» > > Worth nothing the OP's expected is not correct. The result should be > string '$x', as the backslash would

[perl #127226] QUOTE does not remove backslash with adverb :b

On Fri, 23 Jun 2017 05:28:22 -0700, c...@zoffix.com wrote: > On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > > my $x = 42; say Q:s:b{\$x} > > > > # OUTPUT«\42␤» > > # EXPECTED«42␤» > > Worth nothing the OP's expected is not correct. The result should be > string '$x', as the backslash would

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

Yes, it would be awesome to have warnings for unused params and variables. On 2018-01-14 12:16:08, c...@zoffix.com wrote: > On Sat, 14 Oct 2017 20:53:03 -0700, alex.jakime...@gmail.com wrote: > > FWIW I made a throwaway script that looks for unused params, and > > there > > are many > > of these

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

On Sat, 14 Oct 2017 20:53:03 -0700, alex.jakime...@gmail.com wrote: > FWIW I made a throwaway script that looks for unused params, and there > are many > of these in rakudo sources. Of course, most of these cases are not in > hot > paths, but the overall performance benefit may be very noticeable.

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

On Sat, 14 Oct 2017 20:53:03 -0700, alex.jakime...@gmail.com wrote: > FWIW I made a throwaway script that looks for unused params, and there > are many > of these in rakudo sources. Of course, most of these cases are not in > hot > paths, but the overall performance benefit may be very noticeable.

[perl #121843] my @words <== sort <== ("c", "b", "a"); # feed failing to parse

Still reproducible (2017.11, HEAD(5929887)) On 2014-05-10 14:42:47, david.warring wrote: > Golfed from fudged test in integration/advent2010-day10.t > > $ perl6-m -e'my @o <== sort <== ("c", "b", "a")' > Unable to parse expression in quote words;

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

> On 22 Nov 2017, at 19:31, Timo Paulssen via RT > wrote: > On Mon, 20 Nov 2017 12:13:47 -0800, ronaldxs wrote: >> What about a native perl6 range loop? Couldn't there be some way for >> Perl 6 / Rakudo to generate code competitive on a small range with the >>

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

> On 22 Nov 2017, at 19:31, Timo Paulssen via RT > wrote: > On Mon, 20 Nov 2017 12:13:47 -0800, ronaldxs wrote: >> What about a native perl6 range loop? Couldn't there be some way for >> Perl 6 / Rakudo to generate code competitive on a small range with the >>

[perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

On Mon, 20 Nov 2017 12:13:47 -0800, ronaldxs wrote: > What about a native perl6 range loop? Couldn't there be some way for > Perl 6 / Rakudo to generate code competitive on a small range with the > "native-loop" example? > > perl6 -e ' > { > my int ($a, $one, $three) = (42, 1, 3); >

[perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

What about a native perl6 range loop? Couldn't there be some way for Perl 6 / Rakudo to generate code competitive on a small range with the "native-loop" example? perl6 -e ' { my int ($a, $one, $three) = (42, 1, 3); for ^10_000_000 { $a += $one + $a%$three }; say

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

For comparison to march on the same comp: bash-3.2$ perl6 perf.p6 perl6-loop: 63.0037058 c-loop: 76.86853305 (0.82 times faster) native-loop: 0.2170930 (354.08 times faster) perl6 loops are faster. c style loops are slower. Native loops are even faster relative to the others (for me). We can

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

For comparison to march on the same comp: bash-3.2$ perl6 perf.p6 perl6-loop: 63.0037058 c-loop: 76.86853305 (0.82 times faster) native-loop: 0.2170930 (354.08 times faster) perl6 loops are faster. c style loops are slower. Native loops are even faster relative to the others (for me). We can

[perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

On Sun, 12 Mar 2017 07:27:37 -0700, allber...@gmail.com wrote: > On Sun, Mar 12, 2017 at 12:48 AM, Lloyd Fournier > wrote: > > > perl6-loop: 84.8739988 > > c-loop: 67.65849241 (1.25 times faster) > > native-loop: 0.4981954 (135.81 times faster) > > > > Still quite a lot

[perl #132291] [LTA] Too few positionals passed to '' (for [:a] X [:b] -> ($i, $j) { })

Yeah. Fixed in https://github.com/rakudo/rakudo/commit/084078e1c3bd7ca41928f374c26e6a7845db0033. On 2017-11-03 11:08:50, c...@zoffix.com wrote: > Tests: https://github.com/rakudo/rakudo/commit/32412170b3

Re: [perl #132284] [REGRESSION] .gist of a Map was arguably better in the past (say Map.new(‘a’ => ‘b’))

fixed in moarvm commits a9267cb, 650e797, and 676723d. Needs a bump, as well as tests. On 17/10/17 19:28, Zoffix Znet via RT wrote: > On Thu, 12 Oct 2017 22:59:36 -0700, alex.jakime...@gmail.com wrote: >> Code: >> my @a = [1,2,3,4]; my %h = 'a'=>'b','c'=>'d','101'=>'102

[perl #132284] [REGRESSION] .gist of a Map was arguably better in the past (say Map.new(‘a’ => ‘b’))

On Thu, 12 Oct 2017 22:59:36 -0700, alex.jakime...@gmail.com wrote: > Code: > my @a = [1,2,3,4]; my %h = 'a'=>'b','c'=>'d','101'=>'102'; my $c = > \(|@a, |%h); say $c.list; say $c.hash; > > ¦«2015.12»: > (1 2 3 4) > Map.new(("101" => "102",:a(

[perl #132284] [REGRESSION] .gist of a Map was arguably better in the past (say Map.new(‘a’ => ‘b’))

On Thu, 12 Oct 2017 22:59:36 -0700, alex.jakime...@gmail.com wrote: > Code: > my @a = [1,2,3,4]; my %h = 'a'=>'b','c'=>'d','101'=>'102'; my $c = > \(|@a, |%h); say $c.list; say $c.hash; > > ¦«2015.12»: > (1 2 3 4) > Map.new(("101" => "102",:a(

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

And not only parameters, but unused variables also: https://github.com/rakudo/rakudo/blob/ebb0521bd259e9f81e4b127527534090969f398e/src/core/native_array.pm#L1399 On 2017-10-14 20:53:03, alex.jakime...@gmail.com wrote: > FWIW I made a throwaway script that looks for unused params, and there > are

[perl #132306] [PERF] parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

FWIW I made a throwaway script that looks for unused params, and there are many of these in rakudo sources. Of course, most of these cases are not in hot paths, but the overall performance benefit may be very noticeable. There are also cases like this:

[perl #132306] [PERF] subroutine parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

Oh, I guess it applies to methods as well. On 2017-10-14 20:10:15, alex.jakime...@gmail.com wrote: > Code: > sub f1($a, $, $, $, $, $) { 1 }; > my $s; > $s += f1($_, $_, $_, $_, $_, $_) for ^1_000_000; > say now - BEGIN now > > Result: > 0.43209886 > > > Code: > sub f2($a, $b1, $b2, $b3, $b4,

[perl #132306] [PERF] subroutine parameters, even if unused, make stuff slower ( f1($a, $, $, $, $, $) vs f2($a, $b, $c, $d, $e, $f) )

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132306] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132306 > Code: sub f1($a, $, $, $, $, $) { 1 }; my $s; $s += f1($_, $_, $_,

[perl #132291] [LTA] Too few positionals passed to '' (for [:a] X [:b] -> ($i, $j) { })

Oh, but maybe it's worth mentioning that the name was added in this commit: https://github.com/rakudo/rakudo/commit/7783fcab24813054902414f30f6fd4fd60823c30 On 2017-10-13 20:13:01, alex.jakime...@gmail.com wrote: > Code: > for [:a] X [:b] -> ($i, $j) { } > > Result: > Too few

[perl #132291] [LTA] Too few positionals passed to '' (for [:a] X [:b] -> ($i, $j) { })

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132291] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132291 > Code: for [:a] X [:b] -> ($i, $j) { } Result: Too few posit

[perl #132284] [REGRESSION] .gist of a Map was arguably better in the past (say Map.new(‘a’ => ‘b’))

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132284] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132284 > Code: my @a = [1,2,3,4]; my %h = 'a'=>'b','c'=>'d','101'=&

[perl #131925] Smartmatching a junction against a regex object vs m// (‘a’|‘b’ ~~ m/‘a’/)

The problem only appears if `m//` is used directly as the RHS of `~~`: $_ = 'a' | 'b'; say m/a/; # any(｢a｣, Nil) say $_ ~~ m/a/; # False say $_ ~~ { m/a/ }; # any(｢a｣, Nil)

[perl #131925] Smartmatching a junction against a regex object vs m// (‘a’|‘b’ ~~ m/‘a’/)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #131925] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131925 > Code: say so $*DISTRO.Str|$*KERNEL.Str ~~ /linux/ Result: True

[perl #131797] “expected:” and “got:” messages in test output .Str-ify data, that's not entirely right (cmp-ok ‘a’, ‘~~’, /b/)

".gist" is probably the wrong answer in this case. my @got = ‘one’, ‘two three’; say @got # OUTPUT: [one two three] ↑ Not very useful On 2017-07-25 12:52:25, alex.jakime...@gmail.com wrote: > Sometimes it is useful to test the input against regexes. Let's try: > > Code: > use Test; > cmp-ok

[perl #131797] “expected:” and “got:” messages in test output .Str-ify data, that's not entirely right (cmp-ok ‘a’, ‘~~’, /b/)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #131797] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131797 > Sometimes it is useful to test the input against regexes. Let's try:

[perl #127226] QUOTE does not remove backslash with adverb :b

On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > my $x = 42; say Q:s:b{\$x} > > # OUTPUT«\42␤» > # EXPECTED«42␤» Worth nothing the OP's expected is not correct. The result should be string '$x', as the backslash would escape the sigil and prevent it from being interpolated. It actually

[perl #127226] QUOTE does not remove backslash with adverb :b

On Sat, 09 Jan 2016 10:23:18 -0800, gfldex wrote: > my $x = 42; say Q:s:b{\$x} > > # OUTPUT«\42␤» > # EXPECTED«42␤» Worth nothing the OP's expected is not correct. The result should be string '$x', as the backslash would escape the sigil and prevent it from being interpolated. It actually

[perl #130798] A andthen B orelse C orelse D leaks some internal Block

On Fri, 17 Feb 2017 12:41:12 -0800, david.warring wrote: > On Thu, 16 Feb 2017 19:44:47 -0800, lloyd.fo...@gmail.com wrote: > > note (Nil andthen "foo" orelse Nil orelse "bar"); > > -> ;; $_ is raw { #`(Block|140635964425160) ... } > > > > see the previously fixed: > >

[perl #130798] A andthen B orelse C orelse D leaks some internal Block

On Fri, 17 Feb 2017 12:41:12 -0800, david.warring wrote: > On Thu, 16 Feb 2017 19:44:47 -0800, lloyd.fo...@gmail.com wrote: > > note (Nil andthen "foo" orelse Nil orelse "bar"); > > -> ;; $_ is raw { #`(Block|140635964425160) ... } > > > > see the previously fixed: > >

[perl #131111] [@LARRY] %c = %a, %b and @c = @a, @b should behave similarly

bigger difference than a different choice over flattening! In fact, it's pretty consistent throughout Perl 6 that you need to know about the target of an assignment in order to know what it's going to do with the source. Assignment into a List like `($a, $b) = @c` will happily discard unused values,

[perl #131111] [@LARRY] %c = %a, %b and @c = @a, @b should behave similarly

On Thu, 06 Apr 2017 13:46:00 -0700, alex.jakime...@gmail.com wrote: > Code: > my @a = ; > my @b = <1 2 3>; > my @c = @a, @b; > say @c > > Result: > [[a b c] [1 2 3]] > > > So with arrays, nothing is flattened and you get an array with two > element

Re: [perl #131111] [@LARRY] %c = %a, %b and @c = @a, @b should behave similarly

IIRC this hash behavior is deliberate so that hashes can be accumulated. Also, your proposed behavior would require an object hash, not a standard hash; (%a => %b) would necessarily stringify %a. On Thu, Apr 6, 2017 at 4:46 PM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@pe

[perl #131111] [@LARRY] %c = %a, %b and @c = @a, @b should behave similarly

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #13] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=13 > Code: my @a = ; my @b = <1 2 3>; my @c = @a, @b; say @

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

On Sun, Mar 12, 2017 at 12:48 AM, Lloyd Fournier wrote: > perl6-loop: 84.8739988 > c-loop: 67.65849241 (1.25 times faster) > native-loop: 0.4981954 (135.81 times faster) > Still quite a lot of optimization to be done on that front. WRT native int, one of the issues is

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

https://rt.perl.org/Ticket/Display.html?id=130982 > Perl6-style simple a-to-b loops are often much slower than the corresponding C-style loops, especially when dealing with embedded loops. My "real life" example (as far as Project Euler is real life) is: http://pastebin.com/SVYAyA5z It tak

[perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

# New Ticket Created by Michael Schaap # Please include the string: [perl #130982] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130982 > Perl6-style simple a-to-b loops are often much slower than the corresponding C-st

[perl #130798] A andthen B orelse C orelse D leaks some internal Block

On Fri, 17 Feb 2017 12:41:12 -0800, david.warring wrote: > 09:38] r: my $r := do 42 with Nil; say $r.perl; > [09:38] <+camelia> rakudo-moar a162c4: OUTPUT«Empty␤» > [09:38] <+camelia> ..rakudo-jvm fb4f16: OUTPUT«slip()␤» Just a short comment on this: Camelia runs on an older commit (fb4f16 is

[perl #130798] A andthen B orelse C orelse D leaks some internal Block

# New Ticket Created by Lloyd Fournier # Please include the string: [perl #130798] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130798 > note (Nil andthen "foo" orelse Nil orelse "bar"); -> ;; $_ is raw {

[perl #130432] [REGRESSION] Changed behavior when assigning to array but not providing all elements (@b[1, 2, 3] = True)

# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #130432] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130432 > Code: my @b; @b[1, 2, 3] = True; @b.perl.say Result (2015

[perl #130034] A andthen B orelse C leaks some internal Block

On Sun, 06 Nov 2016 20:25:50 -0800, lloyd.fo...@gmail.com wrote: > 15:18 < llfourn_> m: say (Str andthen .uc orelse "foo") # more golfed > 15:18 <+camelia> rakudo-moar 1c425f: OUTPUT«-> ;; $_ is raw { > #`(Block|81391040) ... }␤» > 15:23 < llfourn_> m: say (Str andthen .uc orelse "foo")("wee") >

[perl #128986] [NYI] Forbid \b (backspace) escape sequence in regexes to catch a P5-ism

On Thu, 18 Aug 2016 10:27:04 -0700, sml...@gmail.com wrote: > S05 <http://design.perl6.org/S05.html#line_2234> says: > > Backslash escapes for literal characters in ordinary strings are > allowed in regexes (\a, \x, etc.). However, the exception to this > rule is \b, which i

[perl #130034] A andthen B orelse C leaks some internal Block

Empty isn't passed as an arg. It's just an empty slip that gets flattened, so `orelse` ends up with a single block as the arg (the thunked "foo"), which gets returned. I don't know whether it should be evaluated first. On Wed, 09 Nov 2016 15:52:35 -0800, lloyd.fo...@gmail.com wrote: > Thanks

Re: [perl #130034] A andthen B orelse C leaks some internal Block

Thanks for the update. As viki hinted at, isn't this a bug in itself (andthen problems aside). Why does Empty as the first arg to orelse return a block? say (Empty orelse "foo") -> ;; $_ is raw { #`(Block|140421623865904) ... } Where as say (Any orelse "foo") returns the correct value. On

[perl #130034] A andthen B orelse C leaks some internal Block

On Sun, 06 Nov 2016 20:25:50 -0800, lloyd.fo...@gmail.com wrote: > 15:18 < llfourn_> m: say (Str andthen .uc orelse "foo") # more golfed > 15:18 <+camelia> rakudo-moar 1c425f: OUTPUT«-> ;; $_ is raw { > #`(Block|81391040) ... }␤» > 15:23 < llfourn_> m: say (Str andthen .uc orelse "foo")("wee") >

[perl #130034] A andthen B orelse C leaks some internal Block

# New Ticket Created by Lloyd Fournier # Please include the string: [perl #130034] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=130034 > 15:18 < llfourn_> m: say (Str andthen .uc orelse "foo") # more golfed 15:18 <+camelia>

[perl #127421] : multi sub infix:<==> (Int $a, Str $b) { $a == $b } hangs in COMPILE time

On Fri Jan 29 06:50:08 2016, pawel.pab...@getresponse.com wrote: > multi sub infix:<==> (Int $a, Str $b) { $a == $b } > > Will never finish compilation on Rakudo 6.c and causes severe memory > leak. I found that: > > 1. Types must be different in signature > (Int

[perl6/specs] 151d79: Revert "Forbid Bare C<\b> in Regexes"

hanged paths: M v6d.pod Log Message: --- Revert "Forbid Bare C<\b> in Regexes" This reverts commit b14828bb01abb7e659b9f1a4d43ba572d3a4f173. Per discussion with pmichaud++, this can be added right now, without waiting for 6.d: https://github.

[perl6/specs] b14828: Forbid Bare C<\b> in Regexes

hanged paths: M v6d.pod Log Message: --- Forbid Bare C<\b> in Regexes Implementation to close RT#128986

[perl #128986] [NYI] Forbid \b (backspace) escape sequence in regexes to catch a P5-ism

r literal characters in ordinary strings are allowed in regexes (\a, \x, etc.). However, the exception to this rule is \b, which is disallowed in order to avoid conflict with its former use as a word boundary assertion. To match a literal backspace, use \c8, \x8, or a double-quoted \b.

Re: [perl #128034] [LTA] split() wants something unboxable to a native int but not quite (split ‘b’, ‘aba’, NaN)

ure correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=128034 > > > > Code: > say split ‘b’, ‘aba’, NaN > > Result: > This type cannot unbox to a native integer > in block at -e line 1 > > > OK, that error means that we canno

Re: [perl #128268] "Could not find symbol" error occurs when you use module A::B::C within A::B's class definition

ship between the various units. > > When I try to run test.pl in the tarball, I get the following error: > > > ===SORRY!=== > > Could not find symbol '' > > Disabling precompilation fixes the issue, as does rearranging the contents > of lib/Common/A.pm so that "

[perl #128268] "Could not find symbol" error occurs when you use module A::B::C within A::B's class definition

anging the contents of lib/Common/A.pm so that "use Common::A::B" comes before "unit class Common::A". Removing any seemingly superfluous use statement fixes the issue, so it appears this is one of those wacky dependency graph + precomp bugs. test-module.tar.xz Description: application/xz

[perl #128059] Method-like thingies do not work with indirect object notation (&[leg] ‘a’: ‘b’)

# New Ticket Created by Alex Jakimenko # Please include the string: [perl #128059] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128059 > This works: Code: say ‘a’.&[leg]: ‘b’ Result: Less But this does not: Co

[perl #128034] [LTA] split() wants something unboxable to a native int but not quite (split ‘b’, ‘aba’, NaN)

# New Ticket Created by Alex Jakimenko # Please include the string: [perl #128034] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=128034 > Code: say split ‘b’, ‘aba’, NaN Result: This type cannot unbox to a native inte

[perl #127992] roundrobin has no “:with()” (roundrobin @a, @b, :with(&[==]))

# New Ticket Created by Alex Jakimenko # Please include the string: [perl #127992] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127992 > Code: say zip (1,2,3), (False,False), :with(&[==]) Result: (False False) Code: say

[perl #127421] : multi sub infix:<==> (Int $a, Str $b) { $a == $b } hangs in COMPILE time

# New Ticket Created by Paweł Pabian # Please include the string: [perl #127421] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127421 > multi sub infix:<==> (Int $a, Str $b) { $a == $b } Will never finish co

[perl #127226] QUOTE does not remove backslash with adverb :b

# New Ticket Created by Wenzel Peppmeyer # Please include the string: [perl #127226] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127226 > my $x = 42; say Q:s:b{\$x} # OUTPUT«\42␤» # EXPECTED«42␤»

[perl #127012] LTA error message caused by gather-take eating the line number (gather for ^3 -> $a, $b { take 1 })

# New Ticket Created by Alex Jakimenko # Please include the string: [perl #127012] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127012 > Code: gather for ^3 -> $a, $b { take 1 } Result: ===SORRY!=== Too few posit

Re: Does Perl 6 use $a and $b in sorting?

sort accepts something callable with an arity of 2. Subroutines, blocks and pointies will do: say sort { $^a cmp $^b }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4 5 6)␤» say sort { $^left cmp $^right }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4 5 6)␤» say sort -> $a, $b { $a cmp $b }, 5, 3, 2, 6, 4 OUTPUT«(2 3 4

Does Perl 6 use $a and $b in sorting?

Because of the the special significance of $a and $b in Perl 5's sort comparison, I always avoid using the names in examples, lest it set a booby-trap for later. I've noticed "a" and "b' being used in some P6 examples. Are they no longer significant, or are they just a poor choice of identifier?

[perl6/specs] 982eda: Prevent some confusion re a b c

) Changed paths: M S04-control.pod Log Message: --- Prevent some confusion re a b c

[perl6/specs] bbb0e9: Clarify lack of special meaning of $a,$b in Perl 6

) Changed paths: M S28-special-names.pod Log Message: --- Clarify lack of special meaning of $a,$b in Perl 6

[perl #125335] \b should be quoted in error messages

# New Ticket Created by Alex Jakimenko # Please include the string: [perl #125335] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=125335 Code: say +(\b x 70); Result (in my terminal): Cannot convert stri' (indicated

[perl #123627] [BUG] use A B; gives Cannot invoke null object

# New Ticket Created by Pawel Pabian # Please include the string: [perl #123627] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=123627 22:57 bbkr: r-m: use A B; # LTA error 22:57 camelia: rakudo-moar d78c67: OUTPUT

[perl #120838] [BUG] LTA error message (on JVM) when passing something to named parameter :$b($c)

Status update: It looks like STD's opinion on this has changed: $ viv -c -e 'sub a (:$b($c)) {say $c}; a(:bfoo)' ===SORRY!=== Subsignature not allowed after named parameter; please insert whitespace at (eval) line 1: -- sub a (:$b⏏($c)) {say $c}; a(:bfoo) Parse failed Rakudo's error

[perl #122223] $h = {a = 1, b= 2}; @a = %$h; # not flattening

# New Ticket Created by David Warring # Please include the string: [perl #13] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=13 use Test; my $h = { a = 1, b = 2, c = 3 }; my @h-h = %$h; is_deeply +@h-h, 3

[perl #121253] Cannot use two modules A and B that both use module C on jvm/moar

# New Ticket Created by Tobias Leich # Please include the string: [perl #121253] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=121253 ~/dev/MoarVM$ cat foo.pm say 42 ~/dev/MoarVM$ cat bar.pm use foo; ~/dev/MoarVM$

[perl #120838] [BUG] LTA error message (on JVM) when passing something to named parameter :$b($c)

# New Ticket Created by Carl Mäsak # Please include the string: [perl #120838] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=120838 lizmat_ r: sub a (:$b) {say $b}; a(:bfoo) # this works camelia rakudo-parrot 1049b4

[perl #114362] [BUG] :ignorecase doesn't work with '[A | B]' (but with [A || B])

On Tue Oct 16 10:24:24 2012, jn...@jnthn.net wrote: On Wed Aug 01 05:34:41 2012, fe...@herrmann-koenigsberg.de wrote: felher | r: say BLAR ~~ /:ignorecase [blar | blubb]/ +p6eval | rakudo c1bfbb: OUTPUT«#failed match␤» moritz | it's supposed to match moritz | r: say BLAR ~~

[perl #115278] [BUG] Class B deriving from stubbed-and-then-defined class A doesn't have a .new method, nor a .gist method in Rakudo

# New Ticket Created by Carl Mäsak # Please include the string: [perl #115278] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=115278 masak r: class A { ... }; class B is A {}; class A {}; say B.new; say alive

[perl #115278] [BUG] Class B deriving from stubbed-and-then-defined class A doesn't have a .new method, nor a .gist method in Rakudo

++ has a fix in the backlog: masak r: class A is Any { ... }; class B is A { has A $.foo }; class A { has B $.bar }; say A.new.bar p6eval rakudo 8a07b8: OUTPUT«B()␤» * masak includes this in the ticket

[perl #114362] [BUG] :ignorecase doesn't work with '[A | B]' (but with [A || B])

# New Ticket Created by fe...@herrmann-koenigsberg.de # Please include the string: [perl #114362] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org:443/rt3/Ticket/Display.html?id=114362 felher | r: say BLAR ~~ /:ignorecase [blar | blubb]/

[perl #112202] enum A b c; A.^methods gives too many named arguments: 2 passed, 0 used

Order.WHAT; 16:35 p6eval: rakudo 68e7f8: OUTPUT«Order()␤» 16:35 gfldex: r: say Order.^WHAT; 16:35 p6eval: rakudo 68e7f8: OUTPUT«===SORRY!===␤Cannot use .^ on a non-identifier method call at line 1, near ;␤» 16:36 moritz: r: enum A b c; say A.^methods 16:36 p6eval: rakudo 68e7f8: OUTPUT«too many named

Re: [perl #74654] [BUG] '$b()' is parsed wrongly by Rakudo

Am 11.01.2012 16:46, schrieb Will Coleda via RT: On Tue Aug 17 21:54:31 2010, coke wrote: On Sun Apr 25 07:22:56 2010, masak wrote: JimmyZ masak: alpha is diferent from rakudo JimmyZ masak: which one is right? JimmyZ alpha: my $b =time; say$b(); p6eval alpha 30e0ed: OUTPUT

[perl #75852] [BUG] Can't declare a class A after importing a file which defines a type A::B in Rakudo

On Fri Jun 18 07:36:28 2010, masak wrote: $ cat A/B.pm class A::B {} $ perl6 -e 'use A::B; class A {}' ===SORRY!=== Illegal redeclaration of symbol 'A' $ perl6 -e 'class A::B {}; class A {}; say alive' alive In the failing program, if 'class A::B {}' is replaced by 'role A::B

[perl #74654] [BUG] '$b()' is parsed wrongly by Rakudo

On Tue Aug 17 21:54:31 2010, coke wrote: On Sun Apr 25 07:22:56 2010, masak wrote: JimmyZ masak: alpha is diferent from rakudo JimmyZ masak: which one is right? JimmyZ alpha: my $b = time; say $b(); p6eval alpha 30e0ed: OUTPUT«1272203938.46735␤» JimmyZ rakudo: my $b = time; say $b

[perl #69254] [BUG] Null PMC access when class C does role B is class A in Rakudo

On Thu Mar 11 02:27:51 2010, moritz wrote: I'm pleased to inform you that this awesome and scary features is now implemented correctly, and tested in S14-roles/composition.t This test has regressed in nom. Re-opening. -- Will Coke Coleda

[perl #75632] [BUG] Null PMC access when assigning to the (questionably declared) variable $A::b in Rakudo

On Wed Jun 09 06:17:16 2010, masak wrote: masak std: package A {}; my $A::b p6eval std 31183: OUTPUT«ok 00:01 108m␤» masak hm. masak rakudo: package A {}; my $A::b = 5 p6eval rakudo a54677: OUTPUT«Null PMC access in getprop() [...] * masak submits rakudobug masak rakudo: my $A::b = 5

[perl6/specs] a826b5: [S04,S32] implicit loops expect to be controlled b...

Branch: refs/heads/master Home: http://github.com/perl6/specs Commit: a826b588b613ef61471e4d89c6b86d7f3502dcdb http://github.com/perl6/specs/commit/a826b588b613ef61471e4d89c6b86d7f3502dcdb Author: TimToady la...@wall.org Date: 2010-09-06 (Mon, 06 Sep 2010) Changed paths: M

[perl #74654] [BUG] '$b()' is parsed wrongly by Rakudo

On Sun Apr 25 07:22:56 2010, masak wrote: JimmyZ masak: alpha is diferent from rakudo JimmyZ masak: which one is right? JimmyZ alpha: my $b = time; say $b(); p6eval alpha 30e0ed: OUTPUT«1272203938.46735␤» JimmyZ rakudo: my $b = time; say $b(); p6eval rakudo e393c7: OUTPUT«␤» masak rakudo

[perl #76844] The REPL crashes on class B { method f { ... } }; B.new.f

# New Ticket Created by Gabor Szabo # Please include the string: [perl #76844] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=76844 class B { method f { ... } }; B.new.f Gabor

Re: Suggested magic for a .. b

On Wed, 28 Jul 2010, Darren Duncan wrote: I think that a general solution here is to accept that there may be more than one valid way to sort some types, strings especially, and so operators/routines that do sorting should be customizable in some way so users can pick the behaviour they want.

Re: Suggested magic for a .. b

Martin D Kealey wrote: On Wed, 28 Jul 2010, Darren Duncan wrote: I think that a general solution here is to accept that there may be more than one valid way to sort some types, strings especially, and so operators/routines that do sorting should be customizable in some way so users can pick the

Re: Suggested magic for a .. b

On Sun, Aug 1, 2010 at 11:39 PM, Martin D Kealey mar...@kurahaupo.gen.nz wrote: In any case I'd much rather prefer that the behaviour be lexically scoped, with either adverbs or pragmata, not with the action-at-a-distance that's caused by tagging something as fundamental as a String. In many

Re: Suggested magic for a .. b

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/29/10 08:15 , Leon Timmermans wrote: On Thu, Jul 29, 2010 at 3:24 AM, Darren Duncan dar...@darrenduncan.net wrote: $foo ~~ $a..$b :QuuxNationality # just affects this one test I like that $bar = 'hello' :QuuxNationality # applies

Re: Suggested magic for a .. b

On Thu, Jul 29, 2010 at 9:51 PM, Aaron Sherman a...@ajs.com wrote: My only strongly held belief, here, is that you should not try to answer any of these questions for the default range operator on unadorned, context-less strings. For that case, you must do something that makes sense for all

Re: Suggested magic for a .. b

Please pardon intrusion by a novice who is anything but object oriented. I consider myself a long time user of perl 5. I love it and it has completely replaced FORTRAN as my compiler of choice. Programming Perl is so dog-eared that I may need a replacement. I joined this list when I thought the

Re: Suggested magic for a .. b

On Fri, Jul 30, 2010 at 6:45 PM, Doug McNutt dougl...@macnauchtan.com wrote: Please pardon intrusion by a novice who is anything but object oriented. No problem. Sometimes a fresh perspective helps to illuminate things. Skipping ahead... Are you guise sure that the ... and .. operators in

Re: Suggested magic for a .. b

Aaron Sherman wrote: In the end, I'm now questioning the difference between a junction and a Range... which is not where I thought this would go. Conceptually, they're closely related. In particular, a range behaves a lot like an any() junction. Some differences: 1. An any() junction always

Re: Suggested magic for a .. b

On Wed, Jul 28, 2010 at 10:35 PM, Brandon S Allbery KF8NH allb...@ece.cmu.edu wrote:  On 7/28/10 8:07 PM, Michael Zedeler wrote: On 2010-07-29 01:39, Jon Lang wrote: Aaron Sherman wrote: In smart-match context, a..b includes aardvark. No one has yet explained to me why that makes sense

Re: Suggested magic for a .. b

On Thu, Jul 29, 2010 at 3:24 AM, Darren Duncan dar...@darrenduncan.net wrote: Some possible examples of customization:  $foo ~~ $a..$b :QuuxNationality  # just affects this one test I like that  $bar = 'hello' :QuuxNationality  # applies anywhere the Str value is used What if you compare

Re: Suggested magic for a .. b

On Thu, Jul 29, 2010 at 5:15 AM, Leon Timmermans faw...@gmail.com wrote: On Thu, Jul 29, 2010 at 3:24 AM, Darren Duncan dar...@darrenduncan.net wrote: Some possible examples of customization: $foo ~~ $a..$b :QuuxNationality # just affects this one test I like that $bar = 'hello

Re: Suggested magic for a .. b

is that the most basic approach treats each codepoint as a collection of information and sorts on that information first and then the codepoint number itself. If that's not useful to you, tell Perl what you really wanted. Some possible examples of customization: $foo ~~ $a..$b :QuuxNationality

Re: Suggested magic for a .. b

On 2010-07-28 06:54, Martin D Kealey wrote: On Wed, 28 Jul 2010, Michael Zedeler wrote: Writing for ($a .. $b).reverse - $c { ...} may then blow up because it turns out that $b doesn't have a .succ method when coercing to sequence (where the LHS must have an initial value), just like

Re: Suggested magic for a .. b

Michael Zedeler wrote: This is exactly why I keep writing posts about Ranges being defunct as they have been specified now. If we accept the premise that Ranges are supposed to define a kind of linear membership specification between two starting points (as in math), it doesn't make sense that

Re: Suggested magic for a .. b

Michael Zedeler wrote: This is exactly why I keep writing posts about Ranges being defunct as they have been specified now. If we accept the premise that Ranges are supposed to define a kind of linear membership specification between two starting points (as in math), it doesn't make sense

Re: Suggested magic for a .. b

of reversibility is moot. No thanks; I'd prefer it if $a..$b have analogous meanings in item and list contexts. As things stand, 10..1 means, in item context, numbers that are greater or equal to ten and less than or equal to one, which is equivalent to nothing; in list context, it means an empty

  1   2   3   4   >