-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
More informative error messages when using #[test] or #fmt without std #1127
Comments
Maybe we should automagically link in std when compiling with --test. |
I was hoping for the syntax extension plugin system to materialize and offer a way to declare runtime dependencies, but maybe we should just hack something up for 0.1. It's a common error. |
Both are in core now. I think this is obsolete. |
The test runner is still in std, so I think this is still a problem. |
Not fixed. This still happens when compiling tests for crates that don't |
Yeah, this confused me. |
There are three issues here, which this log shows:
Should we file separate tickets for these three cases? Is 2 here a duplicate of #1448 or is it a distinct bug? Is there any way to make the errors in 3 more clear? If so, is it a general problem and fix that should be a separate github issue? |
I added a distinct ticket about making the tutorial more explicit: #3241 |
I added a separate ticket about the first and fourth error messages which are "unresolved name", because it's not clear which name is unresolved: #3242 |
Compiling with |
Support building with the new Cranelift backends
Currently, you'll get an unexplained
Which is bound to confuse people.
The text was updated successfully, but these errors were encountered: