Skip to content

Prevent emission of (potentially colliding) type aliases in root module for inner types #3202

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jbg
Copy link

@jbg jbg commented Apr 30, 2025

  • Emit aliases in the nearest ancestor module if the parent is not a module, rather than in the root module
  • If an alias would refer to itself, don't emit it (this is really a workaround for the fact that names are sometimes not unique enough, e.g. the header in Inner types are not qualified by namespace so may conflict #2056 produces two items called f_iterator)

jbg added 2 commits April 30, 2025 15:08
 * Emit aliases in the nearest ancestor module if the parent is not a
   module, rather than in the root module
 * If an alias would refer to itself, don't emit it (this is really a
   workaround for the fact that names are sometimes not unique enough,
   e.g. the header in rust-lang#2056 produces two items called f_iterator)
 * Emit aliases in the nearest ancestor module if the parent is not a
   module, rather than in the root module
 * If an alias would refer to itself, don't emit it (this is really a
   workaround for the fact that names are sometimes not unique enough,
   e.g. the header in rust-lang#2056 produces two items called f_iterator)
@jbg jbg force-pushed the jbg/issue-2056 branch from 1fe58f7 to e611aff Compare April 30, 2025 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant