New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
throwing X::AdHoc "Cannot assign to a readonly variable or a value" instead of X::Parameter::RW #4713
Comments
From @cokeMany tests in S03-operators/increment.t are throwing ad hoc exceptions -- |
From @usev6On Sat, 31 Oct 2015 20:35:24 -0700, coke wrote:
There have been some changes in this area: 1) With roast commit Raku/roast@93736e7f73 the failing tests have been changed from expecting X::Parameter::RW to X::Multi::NoMatch. 2) After some recent changes to the multi method cache (Raku/nqp@567f6568f1) only one test in S03-operators/increment.t is failing due to not throwing X::Multi::NoMatch: $ ./perl6-j -Ilib -e 'use Test; throws-like q[my $x = 0; ++++$x], X::Multi::NoMatch' 3) There are three other tests in roast with the same failure mode (and fudged with this ticket number): * https://github.com/perl6/roast/blob/2452b9dce146a98172f4b56cfec14d435fe4e2b1/S04-statements/for.t#L631 I'll adjust the subject of this ticket accordingly and I'll update the fudge messages for the mentioned tests. Also, there are two (failing) tests in S06-traits/misc.t that expect X::Parameter::RW but the test code does not die currently. Those tests are fudged with this ticket number as well, but I think the underlying problem is a bit different and those tests deserve a separate ticket: https://github.com/perl6/roast/blob/aca8689bc407c5461d07a52631ebcaa1f67bebad/S06-traits/misc.t#L48-L54 |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6After rakudo/rakudo@704b893c6a the last tests fudged with this ticket are passing. I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6After rakudo/rakudo@704b893c6a the last tests fudged with this ticket are passing. I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126531 (status was 'resolved')
Searchable as RT126531$
The text was updated successfully, but these errors were encountered: