Skip to content

Regression (?) in name resolution of items defined in functions/blocks #31845

Closed
@petrochenkov

Description

@petrochenkov
Contributor

This code compiles on nightly, but is rejected by stable and beta compilers.
On nightly items defined in a block are visible from all modules defined in this block.
Such "pervasive" visibility is quite unusual and I suspect it was introduced unintentionally.

fn f() {
    struct S;

    fn g() {
        let s = S; // <- beta/stable/nightly - ok
    }
    mod m {
        fn h() {
            let s = S; // <- beta/stable - error: unresolved name `S` [E0425], nightly - ok
        }

        mod n {
            fn k() {
                let s = S; // <- beta/stable - error: unresolved name `S` [E0425], nightly - ok
            }
        }
    }
}

fn main() {
}

cc @jseyfried

Activity

jseyfried

jseyfried commented on Feb 24, 2016

@jseyfried
Contributor

This was introduced in #31105 while fixing #23880.
This bug existed earlier (in some sense) but was benign. Before #31105, only type parameters and local variables leaked, but using these "captured" locals and parameters is already a separate error.

added a commit that references this issue on Feb 26, 2016

Auto merge of #31857 - jseyfried:fix_scoping, r=nikomatsakis

jseyfried

jseyfried commented on Feb 26, 2016

@jseyfried
Contributor

@petrochenkov this can be closed -- I think bors didn't close it because the magic words were only in the title.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @petrochenkov@jseyfried

        Issue actions

          Regression (?) in name resolution of items defined in functions/blocks · Issue #31845 · rust-lang/rust