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

Strange error when declaring a sub with an unknown trait in Rakudo #1668

Closed
p6rt opened this issue Apr 6, 2010 · 5 comments
Closed

Strange error when declaring a sub with an unknown trait in Rakudo #1668

p6rt opened this issue Apr 6, 2010 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Apr 6, 2010

Migrated from rt.perl.org#74092 (status was 'resolved')

Searchable as RT74092$

@p6rt
Copy link
Author

p6rt commented Apr 6, 2010

From @masak

<jnthn> rakudo​: sub yulia is krassivaya { }
<p6eval> rakudo c06062​: OUTPUT«Could not find sub &substr [...]
<jnthn> wtf.
* masak submits rakudobug
<jnthn> Well, it fails anyway.

This should fail, but not with that error.

@p6rt
Copy link
Author

p6rt commented Jul 16, 2010

From @jnthn

On Tue Apr 06 09​:38​:34 2010, masak wrote​:

<jnthn> rakudo​: sub yulia is krassivaya { }
<p6eval> rakudo c06062​: OUTPUT«Could not find sub &substr [...]
<jnthn> wtf.
* masak submits rakudobug
<jnthn> Well, it fails anyway.

This should fail, but not with that error.

Now it fails by telling you about the fact that there's no
trait_mod​:<is> to handle the beautiful trait.

sub yulia is krassivaya { }
No applicable candidates found to dispatch to for 'trait_mod​:<is>'.
Available candidates are​:
...

Which is much more relevant. Given to moritz++ - I guess a test that
trait_mod​:<is> is mentioned somewhere in the error would maybe be a good
idea?

Thanks,

Jonathan

@p6rt
Copy link
Author

p6rt commented Jul 16, 2010

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

@p6rt
Copy link
Author

p6rt commented Jul 15, 2012

From @bbkr

Test in​:

Raku/roast@1a144b773b

@p6rt
Copy link
Author

p6rt commented Jul 15, 2012

@bbkr - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant