-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Control flow analysis broken for never
returning class methods
#56812
Comments
This is working as intended. For performance reasons only specific calls are analyzed. Check #32695 for details. If you change your code according to the requirements it works: const c: Class = new Class();
if (!arg) {
c.throwMethod();
} |
Also duplicates #46254 |
@MartinJohns thanks for the quick reply. Relevant quote from #32695 is:
Another workaround is as follows: function repro1(arg: string | undefined): number {
if (!arg) {
// compatible with return type because the type is `never`, even if the CFA doesn't work
return new Class().throwMethod();
}
return arg.length;
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
π Search Terms
"control flow analysis", "never return"
π Version & Regression Information
never
β― Playground Link
https://www.typescriptlang.org/play?#code/MYGwhgzhAEDC5WgbwLAChrQC4AsBOA9gO4CyAprgQCYAUAlAFzQB2ZAbmXsupproUWgAiAEZhmAcyEBuHtAC+6RWnQAzAK7NgWAJYFm2fMQBim7Xub0mrDl1QZDA4WMkyl6NWd37oeMgAdCAEYaMDwJJggsPB1JaAAfaE0qMlVYsio6bgcdVWgaAEIwiSz7XhYyQXhICHoAOn5ickpaOlkHZUw-LHU8A2K6kDJJXHblTy1vAz9AggAmUPDI6NiJBKTmFLTWTOzMXPyi8NK5PiMiU0mLenbMTt8KXv7wweGJUfc0IA
π» Code
π Actual behavior
When a class method has a
never
return type (seerepro1
function), the control flow analysis ignores this.When a function method has a
never
return type (seerepro2
function), the control flow analysis correctly identifies that this execution branch will end.π Expected behavior
I expected that the function and class method would be treated in the same way by the CFA, because I can't find an obvious reason why they should differ.
Additional information about the issue
No response
The text was updated successfully, but these errors were encountered: