microsoft / microsoft/TypeScript
Non-null assertion should work on possibly-uninitialized auto-typed `let` variables
Open
Nobody has claimed this yet.
Experience Enhancement
Help Wanted
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.4k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Bug Report
🔎 Search Terms
non-null postfix bang implicit any
🕗 Version & Regression Information
- This is the behavior in every version I tried
⏯ Playground Link
💻 Code
let foo;
if (Math.random() > 0.5) {
foo = "hello";
}
// bar: string | undefined, seems fine
let bar = foo;
/* -- pretend I know foo is defined for other reasons -- */
// Error, foo is implicitly any
let baz = foo!;
🙁 Actual behavior
Implicit any on foo!
🙂 Expected behavior
Since the inferred type of foo (as seen in bar) is string | undefined, foo! should trivially have the type string
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked TypeScript Playground and the foo, bar, and baz example, then trace the compiler's inference and non-null assertion handling for an uninitialized let. Done means foo! is accepted with type string rather than producing an implicit-any error, while bar continues to infer string | undefined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100