Herman Venter

We did indeed discuss the need for a flag. Perhaps there is no need for multiple templates in that case. We'll see. I don't recall us discussing the scenarios you...

This seems to be some kind of interaction between optimizing nested functions and joining the state of the local variables of module.

Before we can hope to deal with this, we'll need a range domain (#1066).

Yes, with loops you have to widen and once you widen, precision is lost. Range domains let you regain some of this precision. If you range over an unbounded collection...

We can do weak updates only if there is a join condition that is stable. A widened property name does not fit the bill.

If you want to use the object before the loop, a snapshot should do the trick. I'm not sure if we can do this without the aid of an annotation....

We don't seem to have an existing negative test case for this. The place to add new test would be in test/error-handler.

You would use __abstract. Look at test/error-handler/member2.js for inspiration.

Tried this again and the error is different now: Error: failed to compile `mirai v1.1.0 (D:\a\MIRAI\MIRAI\checker)`, intermediate artifacts can be found at `D:\a\MIRAI\MIRAI\target` Caused by: failed to run custom build...

This seems a bit stale now. Not sure it is fixed, but I've moved on.