hmdne

Not getting into v1.4. Will need to be reworked.

To note a thing - Opal 1.3 supports named captures in web browsers that support it - which means everything modern.

This actually happens to decrease the run time. I anticipated easy gains. Will need some rework.

Idea: If we are to refactor this, shouldn't kwargs be treated similarly to how block is currently handled? I'm not a big fan of defining $$p as a property of...

A problem with this approach I see is that... moving of aliases may be a good idea where we have control, but not where we don't. Opal-Optimizer does this with...

There's another thing I see. Your algorithm, as far as I can see, works this way: - Compile the code first - Collect all calls - Compile again, but without...

Now that I thought about it, how about doing it in reverse? We start from top and don't traverse into defs. After we have collected a number of calls from...

Just for the record, in Opal-Optimizer (which... works well enough for my production codebase to never break :D): A definition is one of the following: - def call - defs...

@janbiedermann this is a thing that we obviously can't support without doing a full evaluation :( for this case we may add a magic comment to note that our code...

(Please ensure you took a look at my edits :D)