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.

Sign up for GitHub

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

Jump to bottom

resolve: More detailed effective visibility tracking for imports #103965

Merged
merged 4 commits into from
Nov 8, 2022
Merged

resolve: More detailed effective visibility tracking for imports #103965

merged 4 commits into from
Nov 8, 2022

Commits on Nov 5, 2022

  1. resolve: More detailed effective visibility tracking for imports 

    Also drop `extern` blocks from the effective visibility table, they are nominally private and it doesn't make sense to keep them there.
    @petrochenkov
    petrochenkov committed Nov 5, 2022
    Configuration menu
    Copy the full SHA
    24093fc View commit details
    Browse the repository at this point in the history

  2. privacy: Print effective visibilities of constructors

    @petrochenkov
    petrochenkov committed Nov 5, 2022
    Configuration menu
    Copy the full SHA
    bb401bd View commit details
    Browse the repository at this point in the history

  3. privacy: Check effective visibility invariants

    @petrochenkov
    petrochenkov committed Nov 5, 2022
    Configuration menu
    Copy the full SHA
    448261a View commit details
    Browse the repository at this point in the history

  4. resolve: Fill effective visibilities for import def ids in a separate… 

    … pass

This should result in less update calls than doing it repeatedly during the fix point iteration.
    @petrochenkov
    petrochenkov committed Nov 5, 2022
    Configuration menu
    Copy the full SHA
    43bea6c View commit details
    Browse the repository at this point in the history