You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Filing mostly to have a single reference point for it, as I saw it brought up a couple of times.
Core point: "optimizer" means entirely optional things executed to gain better speed/memory. However, our static optimizer does things that go beyond that (e.g. compile-time signature checking or literal-to-native handling).
So, we need to create a name to a part of the stuff optimizer does that isn't optional. I don't think it has to be related to any phaser, but we probably should make --optimize=off switch to NOT disable that part.
Off the hip, I propose the name Finalizer for the thing and the Finalizer finalizes things.
Finalize has connotations with DESTROY type actions. Also, it “feels" that this stage would be run after the program has finished (I know it doesn’t, but the naming might give that impression).
How about the “icing” as “icing on the cake" stage? Has a feel of freezing stuff / preparing for final usage.
On 2 Nov 2018, at 15:59, Zoffix Znet ***@***.***> wrote:
Filing mostly to have a single reference point for it, as I saw it brought up a couple of times.
Core point: "optimizer" means entirely optional things executed to gain better speed/memory. However, our optimizer does things that go beyond that (e.g. compile-time signature checking or literal-to-native handling).
So, we need to create a name to a part of the stuff optimizer does that isn't optional. I don't think it has to be related to any phaser, but we probably should make --optimize=off switch to NOT disable that part.
Off the hip, I propose the name Finalizer for the thing and the Finalizer finalizes things.
IRC refs:
• <jnthn> I think we'll rename the optimize phase also:
https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2018-10-25#l160
• Documented "compile time" signature match failure, but it's actually done in "optimize" stage: https://colabti.org/irclogger/irclogger_log/perl6?date=2018-11-02#l340
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Filing mostly to have a single reference point for it, as I saw it brought up a couple of times.
Core point: "optimizer" means entirely optional things executed to gain better speed/memory. However, our static optimizer does things that go beyond that (e.g. compile-time signature checking or literal-to-native handling).
So, we need to create a name to a part of the stuff optimizer does that isn't optional. I don't think it has to be related to any phaser, but we probably should make
--optimize=offswitch to NOT disable that part.Off the hip, I propose the name Finalizer for the thing and the Finalizer finalizes things.IRC refs:
<jnthn> I think we'll rename the optimize phase also:https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2018-10-25#l160
The text was updated successfully, but these errors were encountered: