Skip to content

Changes to determine when to qualify the symbol in given enclosing declaration #30

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

Merged
merged 5 commits into from
Jul 16, 2014

Conversation

sheetalkamat
Copy link
Member

This has changes for determining when to qualify symbol name and also moved the logic of isDeclarationVisible
Still todos are:
error reporting to use the enclosingDeclaration and meaning correctly to report the error message
isDeclarationVisible is setup in checker so it could be used to verify and report errors on visibility of types

… enclosing declaration

Note that this doesnt handle aliases yet.
…ol whose name we are trying to get in the symbol table
…on needs to be emitted

This would help in unifying logic of when to check if the type is visible
else if (node.kind === SyntaxKind.SourceFile) {
return (node.flags & NodeFlags.ExternalModule) ? node : null;
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assert that you won't get here

sheetalkamat added a commit that referenced this pull request Jul 16, 2014
Changes to determine when to qualify the symbol in given enclosing declaration
@sheetalkamat sheetalkamat merged commit fe1fea3 into master Jul 16, 2014
@sheetalkamat sheetalkamat deleted the declarations branch July 16, 2014 22:21
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants