<byteit101[m]>
*around the super-splitter headline
subbu is now known as subbu|away
ur5us has joined #jruby
<enebo[m]>
I will read up a bit
<enebo[m]>
byteit101: so what is the behavior if someone calls super/zsuper explicitly? Error if it cannot match a real constructor?
<enebo[m]>
I guess I believe this is any super which exists will appropriately just call the specified constructor on java side assuming it can bind it properly
<enebo[m]>
In looking at this current WIP I am guessing this does not work yet? That desugar() method in IRMethod will be null by the time you try and JIT
subbu|away is now known as subbu
<enebo[m]>
I am done today but I will see anything written and I will be on in the morning. AST is not where I would like to see this as we would have to retain the AST but a pass for IR might mean thinking quite a bit about accounting for values to super and which instr is for super (since we actually will sometimes just replace super with the method call name when we know it).
<byteit101[m]>
> I guess I believe this is any super which exists will appropriately just call the specified constructor on java side assuming it can bind it properly
<byteit101[m]>
With this work there is nothing to bind to, as we have to pass the args up to the java ctor (the caller of initialize) before resuming the method