Nikolai Tillmann

Related: In order to determine conflicts, `checkThatFunctionsAreIndependent` runs functions multiple times. This is slow, and confusing from a debugging perspective.

The state right where the __optimize call happened. This is currently enabled for special cases like the array `.map` function but is guarded by the `arrayNestedOptimizedFunctionsEnabled` option. This needs to...

In your example above, the `__empty` never gets built into a value that is reachable outside of Prepacked code --- so this is all working alright. (Well, if you look...

I guess the fix is to retain the generator marker as appropriate when synthesizing new Babel function instances for residual functions.

It's an issue. It's likely because generators currently do not form a tree, but a DAG. Until that's fixed, redeclared variables are to be expected.

Fantastic work! You bypass the existing serializer, but then still find the existing `SerializationContext` useful, but then also add some hacks to work with the existing `BabelNodeExpression`s. I wonder if...

And as a plus, the`ResidualHeapVisitor` is completely ignorant of `BabelNodeExpression`s. Ideally, I'd like to move out all build nodes to a Babel-specific place, and instead place specific named instructions in...

Also see https://github.com/ExpoSEJS/Z3 where this is based off of.

Also see https://github.com/Z3Prover/z3/issues/1298.

Sure! I don't actually know what's going on here, but it might be easy...