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

Provide a "qualname" for Entries #2025

Open
scoder opened this Issue Nov 26, 2017 · 0 comments

Comments

Projects
None yet
1 participant
@scoder
Contributor

scoder commented Nov 26, 2017

There are several places in the code base where we check for special cases by name, e.g. for decorators such as @coroutine or builtins. If this happens before the declaration analysis (and sometimes even type analysis), we cannot be sure that they are really referring to a specific global or imported name.

We should add unambiguous qualified names (such as asyncio.coroutine or __builtins__.range) to the symbol table Entry and have an early step where we detect and annotate global names with these qualified names, so that later pipeline steps can rely on them rather than applying their own heuristics and guessing.

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