-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Bad error message using associated type #45447
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
Comments
Could you explain why you think the error message is bad? AFAIK this is intended behaviour: Items (such as |
I see. (The semantics of D language I'm used to create a const instance for each template instantiation). The "outer function" confused me, because there is no outer function. If you think the wording of the error message is acceptable then I will close this issue down. |
Mh, the "outer function" wording seems to be indeed a bit tailored to functions-in-functions, we can keep this issue open I think. |
Current output is buggy:
It should be closer to the following
|
It appears to just blindly do a search for |
This is now fixed. |
I still get this, on Rust 1.43:
|
Can I suggest a clearer message: " |
Is there any fundamental reason for this limitation? I recently found myself wanting to use associated constants in |
@dwrensha This is something that you should probably bring up to T-lang, maybe on Zulip? |
Current output:
|
I think now it's OK to close this issue down. |
I think this code shows a bad error message:
rustc 1.22.0-nightly (4279e2b 2017-10-21) gives:
The text was updated successfully, but these errors were encountered: