Re: Default args in custom constructor

2015-09-05 Thread Philip Hazelden
Oh, I'd been intending to explore that before sending but forgot. Thanks. I currently think that's the best alternative to duplicating defaults, but still more verbose and less intuitive than I'd hope for. On Sat, Sep 5, 2015 at 12:57 AM Timo Paulssen wrote: > Have you considered hash flattenin

[perl #125995] <<...>> returns the wrong structure

2015-09-05 Thread via RT
# New Ticket Created by dakkar # Please include the string: [perl #125995] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=125995 > Example: $ perl6 -e 'dd ' ("a", "b") $ perl6 -e 'dd <>' "a" "b" $ perl6 -e 'dd

[perl #125996] Complex parametric role composition fails badly when no candidate found

2015-09-05 Thread via RT
# New Ticket Created by dakkar # Please include the string: [perl #125996] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=125996 > This code:: role R[$a,$b] {} role R2[$x] does R[1] {} class C does R2[1] {} C.new; P

Re: [perl #125995] <<...>> returns the wrong structure

2015-09-05 Thread Elizabeth Mattijsen
Some elaboration: $ 6 'sub a(@a) { say @a.perl }; a ; a << a b >>' ===SORRY!=== Error while compiling -e Calling a(Str, Str) will never work with declared signature (@a) at -e:1 --> sub a(@a) { say @a.perl }; a ; ⏏a << a b >> Liz === > On 05 Sep 2015, at 12:33, dakkar (via RT

[perl #125997] LTA error message when no parametric role candidate found

2015-09-05 Thread via RT
# New Ticket Created by dakkar # Please include the string: [perl #125997] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=125997 > This code:: role R[$a,$b] {} class C does R[1] {} C.new; Produces the error message::

Re: [perl #125996] Complex parametric role composition fails badly when no candidate found

2015-09-05 Thread Elizabeth Mattijsen
One would expect an error message such as: $ 6 'role R[$a,$b] {}; class C does R[1] {}' ===SORRY!=== No appropriate parametric role variant available for ‘R' but even that message is rather LTA, as it doesn’t mention which parameters were tried and which candidates are available. Liz

[perl #125998] Should IO objects behave like values?

2015-09-05 Thread via RT
# New Ticket Created by dakkar # Please include the string: [perl #125998] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=125998 > This:: '/tmp'.IO eqv '/tmp'.IO returns ``False``. Is this correct? Should IO behave like

Re: [perl #125998] Should IO objects behave like values?

2015-09-05 Thread Elizabeth Mattijsen
> On 05 Sep 2015, at 16:06, dakkar (via RT) > wrote: > > # New Ticket Created by dakkar > # Please include the string: [perl #125998] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/Ticket/Display.html?id=125998 > > > > This:: > > '/tmp'.IO

[perl #126000] infix: is not dynamic enough

2015-09-05 Thread via RT
# New Ticket Created by dakkar # Please include the string: [perl #126000] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126000 > Given this code:: { class Foo { has $.x } multi sub infix:(Foo $a, Foo $b) {

Re: [perl #125998] Should IO objects behave like values?

2015-09-05 Thread Bart Wiegmans
I kind of think that's impossibly complex. What does it even mean for IO objects to be value-equal? They represent unknowns in any case. Even if they resolved to the same file, they might be read at different times and have different contents. Or a write to one object may succeed and another may no

[perl #126000] infix: is not dynamic enough

2015-09-05 Thread jn...@jnthn.net via RT
On Sat Sep 05 07:47:24 2015, dakkar wrote: > Given this code:: > > { > class Foo { has $.x } > > multi sub infix:(Foo $a, Foo $b) { > say "won't get called"; > $a.x eqv $b.x > } > } > > multi sub infix:(Foo $a, Foo $b) { > say "will get called"; > $a.x eqv $

Re: [perl #125998] Should IO objects behave like values?

2015-09-05 Thread Elizabeth Mattijsen
Note that we’re talking really about IO::Path objects here, which is what .IO generates. And in that context, I think an object $a with a given abspath, would be eqv to $b with the same abspath. Because that *is* the identifier on a file system, is it not? Liz = > On 05 Sep

[perl6/specs] 1ec7ab: Start to remove Parcel from S02

2015-09-05 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 1ec7ab1ec91deec8f6c1b8494ba73bcbac3830ec https://github.com/perl6/specs/commit/1ec7ab1ec91deec8f6c1b8494ba73bcbac3830ec Author: Moritz Lenz Date: 2015-09-05 (Sat, 05 Sep 2015) Changed paths: M S02-bi

[perl6/specs] 4c4984: A bit more more De-Parcel-ification

2015-09-05 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 4c498440d7320c4e013382fcc1d4a9b6574fb673 https://github.com/perl6/specs/commit/4c498440d7320c4e013382fcc1d4a9b6574fb673 Author: Moritz Lenz Date: 2015-09-05 (Sat, 05 Sep 2015) Changed paths: M S05-re

[perl6/specs] 650f00: De-Parcel-ify S03

2015-09-05 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 650f0088de4c7a46dcd5f7c44f4f996357d109f7 https://github.com/perl6/specs/commit/650f0088de4c7a46dcd5f7c44f4f996357d109f7 Author: Moritz Lenz Date: 2015-09-05 (Sat, 05 Sep 2015) Changed paths: M S03-op

[perl #126001] Blockless LAST phaser puts Mu in the iteration variable

2015-09-05 Thread via RT
# New Ticket Created by Moritz Lenz # Please include the string: [perl #126001] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126001 > moritz@hack:~/p6/rakudo$ ./perl6-m --version This is perl6 version 2015.07.1-717-ga6bb0ba

[perl6/specs] 558155: De-Parcel-ify S04

2015-09-05 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 558155b811176632b4e00366df2d40c5eeb89cfc https://github.com/perl6/specs/commit/558155b811176632b4e00366df2d40c5eeb89cfc Author: Moritz Lenz Date: 2015-09-05 (Sat, 05 Sep 2015) Changed paths: M S04-co

[perl #126003] Binding Seq to Positional doesn't work with multi

2015-09-05 Thread via RT
# New Ticket Created by Larry Wall # Please include the string: [perl #126003] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126003 > > perl6-m -e 'multi sub foo(@array) { say @array }; foo("abc".comb)' Cannot call foo(Seq);

[perl #126005] UNDO always fires for while, until, loop, and whenever

2015-09-05 Thread via RT
# New Ticket Created by raiph # Please include the string: [perl #126005] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126005 > What I did == while ++$ < 3 { UNDO say 'undo'; say 'done' } What I got == don

Re: bufs and utf8

2015-09-05 Thread Aristotle Pagaltzis
* mt1957 [2015-08-31 19:35]: > I can not do the following; > my Buf $b = 'abc'.encode; > Type check failed in assignment to '$b'; expected 'Buf' but got 'utf8' > > But I can do this; > my Buf $b = 'abc'.encode ~ Buf.new(); > Buf:0x<61 62 63> > > Does the concatenation convert utf8 into Buf? Will t