Suggestion: Add a way to hint typescript about basic function flow (call orders)

Search Terms

"control flow logic", "function call order", "static flow analysis"

Suggestion

Add flow type, for statically declaring some flow logic (order of function calls)

Use Cases

For example, we could tell typescript that the constructor of a React Component will be called before the render, and the render will be called before componentDidMount.

Examples

flow F;

let test: undefined | string;
F1~function first() { //the number of the flow indicates the order.
	test = 'wow';
}

F2~function second() {
	console.log(test.length); // <== ok, second() must come after first() so we know for sure that test was initialized.
}  

example2:

flow LifeCycle;

class Test extends React.Component {
  LifeCycle1~constructor(){...}
  LifeCycle3~componentDidMount(){...}
  LifeCycle2~render(){...}
}

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, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Das Issue nennt keine Dateien, Tests oder Compiler-Einstiegspunkte; beginne damit, die Kontrollflussanalyse von TypeScript und die verknüpften Designziele zu prüfen. Definiere, wie sich eine deklarierte Reihenfolge von Funktionsaufrufen auf die Typprüfung auswirken würde, ohne das ausgegebene JavaScript zu ändern, und überprüfe anschließend die Beispiele zu constructor/render/componentDidMount und zur Variableninitialisierung.