Repository navigation
Variable implicitly has type 'any' in some locations where its type cannot be determined in 5.0 #52401
Description
Bug Report
🔎 Search Terms
locations where its type cannot be determined
🕗 Version & Regression Information
- This changed between versions 4.9 and 5.0
⏯ Playground Link
Playground link with relevant code
💻 Code
let foo;
try {
if (Math.random() > 0.5) {
foo = 1234;
}
} catch {
foo;
}🙁 Actual behavior
Errors like:
Variable 'foo' implicitly has type 'any' in some locations where its type cannot be determined.(7034)
🙂 Expected behavior
No errors
Activity
typescript-bot commentedon Jan 25, 2023
The change between v4.9.4 and main occurred at b7f619d.
jakebailey commentedon Jan 25, 2023
Uh oh. Seems like I should revert that for now.
jakebailey commentedon Jan 25, 2023
I should note that I don't actually know if the error is good or not, it's just new as of my PR above and that wasn't the intent of the change, so I've sent a PR to revert the bad part of the PR for now and we can figure out the rest later.
fatcerberus commentedon Jan 25, 2023
Isn't this a correct error?
foohas an evolving type and can theoretically be accessed (in this case, in thecatchclause) without being assigned, which is what that error generally means.jakebailey commentedon Jan 25, 2023
Yes, I think that might be true (and that's what I'm hearing from those who have looked at this after-hours), but I definitely didn't intend to expose these errors in my catch clause PR (and definitely not inconsistently).