Improving handling of guards

[rvirding]

The LFE compiler handles guards correctly but not as efficiently as possible. One reason is that optimisation passes in the erlang compiler assume that things look exactly like they do from the erlang compiler otherwise they can sometimes do something wrong or even crash. For this reason I have turned off some optimisation passes.

What I plan to do now is rewrite some of the LFE compiler code generation pass to output more erlang compiler like code so I can, hopefully, turn on the optimisation again.

[oubiwann]

A note from the sidelines: This is insanely cool :-)

On Fri, Jan 9, 2015 at 9:32 AM, Robert Virding notifications@github.com
wrote:

The LFE compiler handles guards correctly but not as efficiently as
possible. One reason is that optimisation passes in the erlang compiler
assume that things look exactly like they do from the erlang compiler
otherwise they can sometimes do something wrong or even crash. For this
reason I have turned off some optimisation passes.

What I plan to do now is rewrite some of the LFE compiler code generation
pass to output more erlang compiler like code so I can, hopefully, turn on
the optimisation again.

—
Reply to this email directly or view it on GitHub
#105.

[rvirding]

This was fixed in this commit 5e6dc25 when we went over to the LFE compiler generating Erlang AST.