Never returning functions should disable getter return requirement

Suggestion

declare const error: () => never;
const o = { get p() { error(); } };

Produces the error A 'get' accessor must return a value.(2378). Throwing an error directly would not. I feel similar to https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#better-support-for-never-returning-functions, a never-returning-function should have the same effect.

Afaik "control flow analysis happens before typechecking", so this would only work, when the function has a declared type. That's in line with the linked existing improvement in TS 3.7, and to be expected.

🔍 Search Terms

Getter Get accessor must return a value never returning function error throw

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Commencez par retracer la vérification de la valeur de retour des getters et la gestion du flux de contrôle des fonctions déclarées comme ne retournant jamais, en utilisant la note de version de TypeScript 3.7 comme contexte. Ajoutez une couverture de régression pour un getter qui appelle une fonction déclarée pour retourner never, et vérifiez que le diagnostic du getter est supprimé, tandis que les chemins ordinaires ne retournant pas de valeur exigent toujours une valeur.