Revert "chore: add some static optimization (#294)"

[stephenamar-db]

This partially reverts commit 60db9d0.

This is causing performance regressions

[stephenamar-db]

@He-Pin it's going to be a partial revert, because your optimizations fixed a bug we had with short-circuiting boolean ops.

[He-Pin]

@stephenamar-db Thank you. I think another weird bug left is #331, anyway, we are unlikely to write that code :)

[stephenamar-db]

My gut feeling is that the optimizations around Val.Obj caused them to be evaluated early.

[stephenamar-db]

@stephenamar-db Thank you. I think another weird bug left is #331, anyway, we are unlikely to write that code :)

I'm looking at this too. trying to figure what what needs to be changed in the optimizer to make them work.

[He-Pin]

Cool, I think the bug is if there is an a[x] , where [x] is a params, and then, we should not visit the x which is Id(x) to resolve the parameter, because before evaluation, the x is not binding to the actually value.

That's my guess, and another thing is, we may just pass the Field to the Obj.Comp, because it now contains two cases.
it turn out the slice one is simpler for me to handle :)

[He-Pin]

Maybe we can extract all BinaryOp to a single method with transformBinaryOp, which may help too.
@stephenamar-db

[He-Pin]

@stephenamar-db What's the number after revert this.