perl.perl6.compiler Google Group

[perl #67256] [BUG] Less than awesome error message for failed assignment type checks on subtypes in Rakudo

2009-07-06T12:49:04Z

<masak> rakudo: subset Positive of Num where { $^n > 0 }; my Positive
$p; $p = -42
<p6eval> rakudo 0e8a86: OUTPUT«Assignment type check failed; expected
, but got Int [...]
* masak submits rakudobug
<jnthn> bug?
<jnthn> oh, less than awesome error message
<masak> aye.

[perl #67258] [PATCH] Implement [//] and [||] operators.

2009-07-06T14:36:59Z

This is my crack at implementing these two operators. I'm looking for
feedback since I've never written for Rakudo before.
Thanks.
Kyle.

Re: [pugs-commits] r27435 - t/spec/S12-attributes

2009-07-06T06:44:44Z

I suspect that at some point we'll get a bunch of error classes/roles,
so that you can say
ok $! ~~ XX::DivideByZero;
Or something along these lines. We just need somebody to figure out a
good structure, and spec it.
+1
This is much more sane for now.
When no 'self' is found, it means that we're not in a class. So the

Re: [pugs-commits] r27435 - t/spec/S12-attributes

2009-07-06T04:55:04Z

I agree it's fragile for exactly that reason. I wrote the test as I
did to make sure that it's an error related to the problem the code is
showing. For example, an earlier iteration of this test died with the
error "Re-declaration of type X" because I was using the same name
everywhere. I've already found a test that was supposed to die for

Re: [pugs-commits] r27435 - t/spec/S12-attributes

2009-07-06T04:33:46Z

...I suspect that the spectests should not be checking for
specific error text. At least I hope that's the case, unless
all implementations are going to standardize error messages.
(I'm fine with us standardizing on exception types, which we
haven't done yet, but requiring specific error messages seems

[perl #67122] tests available

2009-07-05T14:53:05Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S05-metasyntax/charse t.t

[perl #62836] tests available

2009-07-05T14:53:04Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S02-builtin_data_type s/lists.t

[perl #67024] tests available

2009-07-05T14:53:06Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S12-methods/multi.t

[perl #60408] tests available

2009-07-05T14:53:07Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S06-signature/positio nal.t

[perl #67218] tests available

2009-07-05T14:53:08Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S02-builtin_data_type s/pair.t

[perl #67124] tests available

2009-07-05T14:53:03Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S05-metasyntax/charse t.t

[perl #67236] tests available

2009-07-05T14:53:10Z

This is an automatically generated mail to inform you that tests are now available in t/t/spec/S12-attributes/recurs ive.t

[perl #67236] [BUG] can't push to an attribute array typed with the class it's in in Rakudo

2009-07-05T11:25:01Z

<masak> next one :)
<jnthn> rakudo: my $a = undef; say $a.PARROT; say undef.PARROT;
<p6eval> rakudo 6a4d66: OUTPUT«Failure␤Failure␤»
<masak> rakudo: class A { has A @.as is rw }; my $x = A.new; $x.as[0]
= A.new; say $x.as.perl
<p6eval> rakudo 6a4d66: OUTPUT«[A.new()]␤»
<masak> this works fine.

[perl #67234] [BUG] smartmatching undef against a regular expression breaks in Rakudo

2009-07-05T11:15:33Z

<masak> jnthn: hello. I've been coding a lot since I left last night.
<masak> have a few new bugs to report.
<masak> rakudo: undef ~~ /foo/
<p6eval> rakudo 6a4d66: OUTPUT«Object must be created by a class.␤in
regex PGE::Grammar::_block50 [...]
<masak> I consider this a rakudobug.
<jnthn> Hmm, that's quite a wtf one.

[perl #67222] [BUG] the value of $/ in closures in the second argument of .=subst calls is all wrong in Rakudo

2009-07-04T17:34:33Z

<masak> rakudo: $_ = "(foo,bar,(baz))"; .=subst( /<-[(),]>+/, { "'$/'"
<p6eval> rakudo 6a4d66: OUTPUT«Use of uninitialized value␤Use of
uninitialized value␤Use of uninitialized value␤('','',(''))␤»
<masak> that can't be right.
<pmichaud> I suspect the .=subst
* masak submits rakudobug
<zulon> even with another var ($x eg) this still gives the same result