Skip to content

Allow nonNullAssertions on possibly-uninitialized auto-typed let variables #52483

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Tobias-Scholz
Copy link
Contributor

Fixes #52439

@typescript-bot typescript-bot added the For Backlog Bug PRs that fix a backlog bug label Jan 29, 2023
@Tobias-Scholz
Copy link
Contributor Author

@microsoft-github-policy-service agree

@Tobias-Scholz Tobias-Scholz marked this pull request as ready for review January 29, 2023 01:12

// @strict: true

//@ts-ignore
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is there a //@ts-ignore here? I don't think you need that in the test.

@sandersn
Copy link
Member

sandersn commented May 2, 2025

This has been sitting for a couple of years. @Tobias-Scholz unless you want to start working on it again, I'd like to close it for housekeeping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
For Backlog Bug PRs that fix a backlog bug
Projects
Status: Waiting on reviewers
Development

Successfully merging this pull request may close these issues.

Non-null assertion should work on possibly-uninitialized auto-typed let variables
5 participants