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
when digging into the package namespace of a type capture in Rakudo #3506
Comments
From @masak<Ven> Oooh, I got a segfault! Code inlined for great justice: role Zero { subset _0 of Zero; say Suc[Suc[Suc[Zero]]]::count; <masak> there's probably something submittable in there, but it It does make sense to :: into a type capture, as Ven's bigger example |
From @usev6The segfaults are mostly gone. Only on parrot there is a Null PMC Access, but only for two of the four examples. With said two examples there is an (non segfaulting) error on Moar and JVM as well: $ perl6 -e 'role S[::N] { N::x }' ## no error on Moar, Parrot and JVM $ perl6 -e 'sub foo(::N) { N::x }' ## no error on Moar, Parrot and JVM $ perl6-m -e 'my (::N); N::x' $ perl6-j -e 'my (::N); N::x' $ perl6-p -e 'my (::N); N::x' $ cat 122716.pl6 $ perl6-m 122716.pl6 $ perl6-j 122716.pl6 $ perl6-p 122716.pl6 |
1 similar comment
From @usev6The segfaults are mostly gone. Only on parrot there is a Null PMC Access, but only for two of the four examples. With said two examples there is an (non segfaulting) error on Moar and JVM as well: $ perl6 -e 'role S[::N] { N::x }' ## no error on Moar, Parrot and JVM $ perl6 -e 'sub foo(::N) { N::x }' ## no error on Moar, Parrot and JVM $ perl6-m -e 'my (::N); N::x' $ perl6-j -e 'my (::N); N::x' $ perl6-p -e 'my (::N); N::x' $ cat 122716.pl6 $ perl6-m 122716.pl6 $ perl6-j 122716.pl6 $ perl6-p 122716.pl6 |
@usev6 - Status changed from 'new' to 'open' |
From @cokeOn Sat Jan 24 14:17:53 2015, bartolin@gmx.de wrote:
With the segfaults gone, this bug report is closable. (For extra points, try to make sure that the failure mode is correct, but that's not mandatory to close the ticket.) -- |
Migrated from rt.perl.org#122716 (status was 'open')
Searchable as RT122716$
The text was updated successfully, but these errors were encountered: