feat: Add special form expression optimizations

[pramodsatya]

WIP: Please do not review

[netlify]

✅ Deploy Preview for meta-velox ready!

Name	Link
🔨 Latest commit	46ebde5
🔍 Latest deploy log	https://app.netlify.com/sites/meta-velox/deploys/67c0c1f875a5f40008dcd69f
😎 Deploy Preview	https://deploy-preview-12474--meta-velox.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Yuhta]

Why not doing it when we compile the expressions? exec::Expr is meant to be runtime expressions and constant folding should be finished before it.

[pramodsatya]

Why not doing it when we compile the expressions? exec::Expr is meant to be runtime expressions and constant folding should be finished before it.

Thanks for the suggestion @Yuhta, but I don't quite follow. The virtual function constructSpecialForm in FunctionCallToSpecialForm is called by the expression compiler in ExprCompiler.cpp -> compileExpressions() -> compileRewrittenExpression(). When an expression like (1 = 2) and (2 != 4) is compiled for instance, it will have as inputs ConstantExprs with values false and true because the input expressions to core::CallTypedExpr AND are constant folded during compilation. So when the function ConjunctCallToSpecialForm::constructSpecialForm() is called by the expression compiler, this optimization intends to return a ConstantExpr with value false instead of the AND ConjunctExpr when any of the inputs is (or has been constant folded to) false.
Could you please elaborate where in the expression compiler the changes should be moved to?