Clarify use_decl module resolution docs. #8639
Conversation
|
@singingboyo Looks like one of the doc tests failed. Maybe mark it as |
|
Marked the new example It does compile if |
|
@singingboyo: you could use the ability to ignore lines to wrap the code in a function and set |
|
Turns out there's no need for a wrapper function, just needed a semi-colon after It's all squashed to a single, working commit now. |
|
@singingboyo: yeah it's a bit strange, with the semi-colon it applies to the enclosing scope (in this case - a |
Attempt #2 of [this pull request](#8597) since my tired mind decided messing up my repo, then deleting and re-forking was a good idea. This is identical to the second last commit in that PR. (The one before I ruined everything.) This is an improvement to use_decl docs, which will hopefully improve understanding of how resolution works and where `extern mod` and module declarations should go to make them visible to use declarations.
…, r=dswij `trivially_copy_pass_by_ref` fixes fixes rust-lang#5953 fixes rust-lang#2961 The fix for rust-lang#5953 is overly aggressive, but the suggestion is so bad that it's worth the false negatives. Basically three things together: * It's not obviously wrong * It compiles * It may actually work when tested changelog: Don't lint `trivially_copy_pass_by_ref` when unsafe pointers are used. changelog: Better track lifetimes when linting `trivially_copy_pass_by_ref`.
Attempt #2 of this pull request since my tired mind decided messing up my repo, then deleting and re-forking was a good idea. This is identical to the second last commit in that PR. (The one before I ruined everything.)
This is an improvement to use_decl docs, which will hopefully improve understanding of how resolution works and where
extern modand module declarations should go to make them visible to use declarations.