Migration of Integer to inline

[Mateusz Romanowski]

Hi All,
I have been re-reading *state of valhalla* and following the discussions
regarding *inline-friendly* abstract classes.

If non-Object abstract class as superclass of inline class is allowed, the
migration story for Optional seems easy.
It would be the same for Integer, if only there were no pesky public
Integer::new...

Could you share any preliminary thoughts how the classfiles (found in
*dusty* jars) that use the Integer constructor would be treated?

Is it feasible to have the bytecode weaved to replace the new-dup-init
sequence during class loading?

Thanks,
Mateusz