Skip to content
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

Unknown type error being hidden in trait definittion. #4426

Open
p6rt opened this issue Jul 21, 2015 · 3 comments
Open

Unknown type error being hidden in trait definittion. #4426

p6rt opened this issue Jul 21, 2015 · 3 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jul 21, 2015

Migrated from rt.perl.org#125662 (status was 'open')

Searchable as RT125662$

@p6rt
Copy link
Author

p6rt commented Jul 21, 2015

From @jonathanstowe

multi trait_mod​:<is>(Routine $r, :$foo!) { $r does Foo; }; class Bar { method boom() is foo {}; };

Gives rise to ye olde​:

===SORRY!=== Error while compiling -e
Cannot invoke this object (REPR​: Null, cs = 0)
at -e​:1

In fact any combination where a "type object" is used in this place that isn't defined​:

multi trait_mod​:<is>(Routine $r, :$foo!) { Bar }; sub boom is foo {}

does the same.

I thought that I had reported this before but it seems not.

There seems to be a whole category of the errors being ignored and it ploughing on in a broken state like this.

@p6rt
Copy link
Author

p6rt commented Dec 3, 2017

From @AlexDaniel

Still reproducible (2017.11,HEAD(e5b660e)), with slightly different message​:

===SORRY!=== Error while compiling -e
Cannot invoke this object (REPR​: Null; VMNull)
at -e​:1

On 2015-07-21 11​:54​:54, jns+bc@​gellyfish.co.uk wrote​:

multi trait_mod​:<is>(Routine $r, :$foo!) { $r does Foo; }; class Bar {
method boom() is foo {}; };

Gives rise to ye olde​:

===SORRY!=== Error while compiling -e
Cannot invoke this object (REPR​: Null, cs = 0)
at -e​:1

In fact any combination where a "type object" is used in this place
that isn't defined​:

multi trait_mod​:<is>(Routine $r, :$foo!) { Bar }; sub boom is foo {}

does the same.

I thought that I had reported this before but it seems not.

There seems to be a whole category of the errors being ignored and it
ploughing on in a broken state like this.

@p6rt
Copy link
Author

p6rt commented Dec 3, 2017

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant