Max Graey

Yes, negative denonimators quite uncommon especially those who might have benefited from negative value. Besides, it would make the logic very complicated if we take this into account

@kripken Can we merge it?

@tlively @kripken Could you merge it while it already approved?

> A few large real-world wasm files would be enough. I can help find some if you need that It should be non-LLVM binaryen due to LLVM already do this...

I believe that any ambiguity that might create undefined behaviour or very different behaviour should produce an error. JS design especially as far as errors is concerned should be avoided...

More example: ```ts // nested call (without diagnostics errors) function b(x: () => void): () => void { return x } let value = b (() => console.log('Hello'))() ```

Hmm, perhaps we can support reassignment for static function members. Will add note

generalize to: ```rust u32(x) < C -> 1, iff maxBits(x) < maxBits(C) u32(x) 1, iff maxBits(x) < maxBits(C) ```

Special case: ``` x == -1 => 0 if maxBits(x) != bits(-1) ```

> However, inlining will achieve similar results if the called function is small enough, so I'm not sure how much that would help in practice on real-world code. Yes, if...