-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Misleading error message for bad export statement #1908
Comments
Also, we don't need to write 'error' a second time. |
And maybe also enclose the id in backticks, like in |
Yeah, should use backticks. I happened to remove the extra 'error' in a cleanup fit yesterday. |
The error message comes from resolve, so assigning @marijnh |
Had to make some changes to keep the example up to date, but note that it compiles despite the fact that it exports something that doesn't exist.
Compiled with |
Blocked on #1893 (export statements will go away altogether). |
Since exports are on the way out, this is obsolete. |
…5,giraffate Use `.into_iter()` rather than `.drain(..)` Replacing `.drain(..)` with `.into_iter()` makes my project's binary size smaller. Fixes rust-lang#1908 Applicability of this suggestion is `MaybeIncorrect` rather than `MachineApplicable` due to the complexity of "checking otherwise usage" X-| changelog: Add new lint [`iter_with_drain`]
* Use different type in an example Sentences such as «without the argument u32» were ambiguous, as there were two distincts u32. Having a single one, the one in the monomorphization of the type, remove the ambiguity. * Update src/ty.md --------- Co-authored-by: Nilstrieb <48135649+Nilstrieb@users.noreply.github.com>
* Use different type in an example Sentences such as «without the argument u32» were ambiguous, as there were two distincts u32. Having a single one, the one in the monomorphization of the type, remove the ambiguity. * Update src/ty.md --------- Co-authored-by: Nilstrieb <48135649+Nilstrieb@users.noreply.github.com>
An 'id' isn't a language concept so probably shouldn't appear in the UI. Maybe 'identifier', or even 'enum' if we actually know this is checking enums.
The text was updated successfully, but these errors were encountered: