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
Error when attempting to use a package that has one of core namespaces in its name #5815
Comments
From winexpertu@yandex.ruVersion: Rakudo version 2016.11 built on MoarVM version 2016.11 implementing Perl 6.c. Example of the issue: package Attribute::Foo { }; Attempting to compile such code produces a misleading error message: "Attribute::Foo is a builtin type, not an external module". |
From @zoffixznetThe error is even weirder here: m: package IO::Foo { }; use IO::Foo |
From @zoffixznetOn Mon, 28 Nov 2016 05:38:23 -0800, cpan@zoffix.com wrote:
Oh, that one was just a glitch in camelia. The error is the same for IO:: as for Attribute:: m: package IO::Foo { }; use IO::Foo |
From @zoffixznetOn Mon, 28 Nov 2016 05:41:48 -0800, cpan@zoffix.com wrote:
One more issue in this bunch, caused by presence of `role X` and invalid method call: $ perl6 -e 'class Foo { role X {}; method z { Foo!z } }' |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Wed, 27 Dec 2017 05:17:34 -0800, cpan@zoffix.com wrote:
$ perl6 -v $ cat Foo.pm6 $ perl6 -I. -MFoo -e 'say Foo::Z::Bar; say Foo::X::Meow' $ pico Foo.pm6 ... $ cat Foo.pm6 $ perl6 -I. -MFoo -e 'say Foo::Z::Bar; say Foo::X::Meow' Another related case. Namespace of inner class begins with core namespace is not found, but with class's namespace then found. |
I just also ran into this issue, it's still a problem and it's quite confusing behavior |
I think we need to keep this in mind with the RakuAST work. |
This works around Raku/old-issue-tracker#5815
Migrated from rt.perl.org#130200 (status was 'open')
Searchable as RT130200$
The text was updated successfully, but these errors were encountered: