-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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 better display experience for unresolved values and types #39032
Labels
In Discussion
Not yet reached consensus
Rescheduled
This issue was previously scheduled to an earlier milestone
Suggestion
An idea for TypeScript
Milestone
Comments
This was referenced Jun 12, 2020
DanielRosenwasser
added
Suggestion
An idea for TypeScript
In Discussion
Not yet reached consensus
labels
Jun 12, 2020
RyanCavanaugh
added
the
Rescheduled
This issue was previously scheduled to an earlier milestone
label
Aug 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
In Discussion
Not yet reached consensus
Rescheduled
This issue was previously scheduled to an earlier milestone
Suggestion
An idea for TypeScript
Today, an unresolved type, or the type of an unresolved variable will look something like
any
. Internally, these resolve to a well-known error type that semantically acts asany
.However, in #37713, we may not have a full picture of the world because we're limited to a single file.
I think we should consider doing two things
any
-like type calledloading
.According to @CyrusNajmabadi, Roslyn already does something really similar to this.
The text was updated successfully, but these errors were encountered: