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
Null PMC access when two methods from different roles collide in a class composition in Rakudo #1512
Comments
From @masak<masak> rakudo: role A { method x {} }; role B { method x {} }; class |
From @bbkrOn Kiev build $ perl6 -e 'role A { method x {} }; role B { method x {} }; class C does Adding tests... |
The RT System itself - Status changed from 'new' to 'open' |
From @bbkrtests added in S14-roles/composition.t |
@bbkr - Status changed from 'open' to 'resolved' |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S14-roles/composition.t commit 4ed0890c3ab73914cd23c087304be9ac37e09268 [t/spec] tests for RT #72856 Null PMC access when two methods from different roles collide in a class composition in Rakudo Inline Patchdiff --git a/t/spec/S14-roles/composition.t b/t/spec/S14-roles/composition.t
index ca5b4cc..73850b7 100644
--- a/t/spec/S14-roles/composition.t
+++ b/t/spec/S14-roles/composition.t
@@ -1,6 +1,6 @@
use v6;
use Test;
-plan 22;
+plan 23;
# L<S14/Roles/"Roles may be composed into a class at compile time">
@@ -107,6 +107,14 @@ ok rB !~~ RT64002, 'role not matched by second role it does';
}
+# RT #72856
+{
+ role RT72856A { method foo {} };
+ role RT72856B { method foo {} };
+ eval 'class RT72856C does RT72856A does RT72856B {}';
+ ok $! ~~ /foo .* collides/,
+ 'method of the same name from two different roles collide in a class composition';
+}
done_testing;
|
From @cokeOn Mon Jun 28 15:34:12 2010, bbkr wrote:
Regressed in nom. Re-opening ticket. -- |
@coke - Status changed from 'resolved' to 'open' |
From @moritzworks again, tests pass |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#72856 (status was 'resolved')
Searchable as RT72856$
The text was updated successfully, but these errors were encountered: