Name already in use

Emscripten lowered the default stack size of emitted modules to 64kb recently, easily producing stack overflows in the optimizer. This version of Binaryen increases stack size to the previous 5mb again.

BREAKING CHANGE: Use of global variables (in the Wasm sense) is now checked more strictly to prevent undesirable execution order. If the compiler detects that it is possible that a variable might not have been initialized when accessed, a diagnostic is produced. It cannot be ruled out that some amount of existing code will be affected, since such checks are performed at runtime in JS but are proven at compile time in AS. If encountered, the fix is to move the variable's declaration up, say before the first invocation of a function (that might call another function) accessing the variable, so it is guaranteed that it is initialized before its first use.

BREAKING CHANGE: Binary and ternary expressions now compute and evaluate to the least upper bound of two not identical class type inputs in the absence of a better fitting contextual type. Technically a breaking change, yet likely without noticeable effects on existing code.

BREAKING CHANGE: Initialization of global variables sometimes wasn't guaranteed before, allowing unsafe behavior if initialization indeed wasn't performed before access. To mitigate, variables from now on require either an initializer, a primitive type with a trivial default value (typically `0`), a nullable type (if a reference, defaulting to `null`) or otherwise annotation with definitive assignment (i.e. `let someObject!: ...`, then inserting a runtime check upon access).