You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
interfaceA{}functionfoo(a:A){if('abc'ina){constz=a;// Element implicitly has an 'any' type because expression of type '"abc"' can't be used to index type 'A'.// Property 'abc' does not exist on type 'A'.returnz['abc'];}}
🙁 Actual behavior
Compiler gives an error that you cannot index into type 'A', since 'abc' does not exist in type 'A'
🙂 Expected behavior
Compiler recognizes the existence check and does not give an error.
Observation
This seems to be caused by the improvement in the control flow analysis/type inference. Before the type of z in the below example was 'never' prior to TS4.3, but now the compiler recognizes z being type A
Question : I have one question though, is it by design that it's allowed to index into never types?
The text was updated successfully, but these errors were encountered:
Caused by #38610, which is specifically about not narrowing to never. As I said above, I think the current behavior is more desirable, but I suppose it is a breaking change. But really, anything relying on the old behavior seems suspicious given that you can index never with anything and not see an error. The issue that #38610 fixes is that never isn't a correct reflection of the in check. The check absolutely could succeed since pretty much anything is assignable to {}.
Bug Report
Cannot bracket-index into an object after checking it's existence on that object.
The same failure was reported in #43651, but I couldn't find a separate discussion or a ticket for this.
🔎 Search Terms
🕗 Version & Regression Information
Worked in 4.2.4. Starts to break since 4.3.0-beta
⏯ Playground Link
Playground link
💻 Code
🙁 Actual behavior
Compiler gives an error that you cannot index into type 'A', since 'abc' does not exist in type 'A'
🙂 Expected behavior
Compiler recognizes the existence check and does not give an error.
Observation
This seems to be caused by the improvement in the control flow analysis/type inference. Before the type of
z
in the below example was 'never' prior to TS4.3, but now the compiler recognizes z being typeA
Question : I have one question though, is it by design that it's allowed to index into
never
types?The text was updated successfully, but these errors were encountered: