Description

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!;

Contributor guide

Tech stack

typescript

Domain

tooling

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

5

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

over 1 week

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

TypeScript type systemnon null assertion semanticsbasic compiler source familiarity

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

10

Research direction

The issue reports that the non null assertion operator (!) does not work on possibly uninitialized auto typed let variables, causing an implicit any error. The expected behavior is that `foo!` should resolve to `string` given that `foo` is inferred as `string | undefined`. To fix this, one would need to examine how the TypeScript compiler handles type inference for uninitialized let variables and how the non null assertion operator interacts with them. Relevant code areas likely include the type checker's handling of assignments and the narrowing of possibly uninitialized variables. The playground link and code sample provide a minimal reproduction. No linked PRs or assignees exist, so the issue is open for contribution. Research should focus on the compiler's flow analysis for let variables without initializers and the implementation of the non null assertion in the type checker.