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

Document uniform_paths #487

Open
petrochenkov opened this issue Dec 27, 2018 · 3 comments
Open

Document uniform_paths #487

petrochenkov opened this issue Dec 27, 2018 · 3 comments
Labels
A-resolve Name resolution, paths, namespaces, preludes, etc. RFC Stabilization Docs Documentation required for stabilizing a feature
Milestone

Comments

@petrochenkov
Copy link
Contributor

This is a documentation issue for rust-lang/rust#56759

@Centril Centril added S-waiting-on-stabilization Waiting for a stabilization PR to be merged in the main Rust repository RFC Stabilization Docs Documentation required for stabilizing a feature labels Dec 28, 2018
@Centril Centril added this to the 1.32 milestone Jan 12, 2019
@ehuss ehuss removed the S-waiting-on-stabilization Waiting for a stabilization PR to be merged in the main Rust repository label Jan 27, 2019
@ehuss ehuss added the A-resolve Name resolution, paths, namespaces, preludes, etc. label Aug 30, 2019
@estebank
Copy link
Contributor

Some information around 2018 edition has been added to https://github.com/rust-lang/reference/blob/master/src/items/use-declarations.md. Is the current state of the documentation enough to close this ticket @petrochenkov?

@ehuss
Copy link
Contributor

ehuss commented Apr 23, 2020

We just undocumented it (#665), because it was wrong in several ways. There is an open PR #697 to update it, but I think the PR is still incomplete, and doesn't really address the underlying issue. Personally, I don't think it can be properly documented without documenting all of name resolution, which is a huge project.

@bstrie
Copy link
Contributor

bstrie commented Apr 25, 2021

One subtask of this is to document the limitations of type aliases WRT associated items (including enum variants, which are secretly associated items):

mod my_mod {
    pub enum MyEnum {
        MyVariant
    }
    pub type TypeAlias = MyEnum;
}
use my_mod::MyEnum; // OK
use my_mod::MyEnum::MyVariant; // OK
use my_mod::TypeAlias; // OK
use my_mod::TypeAlias::MyVariant; // Doesn't work
let _ = my_mod::TypeAlias::MyVariant; // OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-resolve Name resolution, paths, namespaces, preludes, etc. RFC Stabilization Docs Documentation required for stabilizing a feature
Projects
None yet
Development

No branches or pull requests

5 participants