Remove resolveLocation from the checker #3919
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… in the sequence have types
…ype arguments present
| // a/**/ | ||
| // } | ||
| // } | ||
| // getTypeOfSymbol for a would return type of parameter symbol string | number |
There was a problem hiding this comment.
for a would return type
… remove_resolveLocation
|
@DanielRosenwasser I've addressed your feedback. |
|
Looks great |
JsonFreeman
added a commit
that referenced
this pull request
Jul 21, 2015
Remove resolveLocation from the checker
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I removed the resolveLocation function from the checker. I fixed all resulting regressions in what I think are better ways.
Two side effects of my change