Resolve more jsdoc value references as types#34515
Merged
Conversation
weswigham
approved these changes
Oct 16, 2019
Member
weswigham
left a comment
There was a problem hiding this comment.
Honestly wish we could do away with the value fallback stuff entirely at some point though. Alas. :(
Member
Author
|
I mean, we need something, but a value fallback is probably a backward way of looking at "in JS, we wish that more values had associated types". |
Member
|
Right - which, generally, probably means binding way more assignments as aliases, if possible. |
This was referenced Oct 23, 2019
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
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.
Fixes #33106