Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃 Pick PR #42626 (No did-you-mean-to-call error on ca...) into release-4.2 #42780

Merged

Conversation

typescript-bot
Copy link
Collaborator

This cherry-pick was triggered by a request on #42626
Please review the diff and merge if no changes are unexpected.
You can view the cherry-pick log here.

cc @DanielRosenwasser

Component commits:
214ef0c No did-you-mean-to-call error on casts
I chose to do the ad-hoc check rather than yet another tree walk.

1. It's faster to run and easier to read.
2. This error came from looking at real code. It happened twice, so I
think the best estimate for other uses that happened zero times is in
fact zero.
3. I couldn't think of other places to put the cast, given the
restrictions on `testedNode` just before the new code.

1d34778 Merge branch 'master' into no-did-you-mean-to-call-error-on-casts
@typescript-bot typescript-bot added the For Uncommitted Bug PR for untriaged, rejected, closed or missing bug label Feb 12, 2021
@typescript-bot
Copy link
Collaborator Author

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

@DanielRosenwasser DanielRosenwasser merged commit 7f64b3a into microsoft:release-4.2 Feb 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants