Unknown type error being hidden in trait definittion.

[p6rt]

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

Searchable as RT125662$

[p6rt]

From @jonathanstowe

multi trait_mod​:\(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​:\(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]

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​:\(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​:\(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]

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