On Friday, 21 November 2025 at 15:25, Arnaud Le Blanc <[email protected]> wrote:
> Regarding the impact of the JIT on internal development, I believe > that it's relatively low: > > * The JIT is known to be a bit unstable yet, and there are occasional > JIT bug reports, but these affect only the JIT and deployments with > JIT enabled > * Changes to the VM are likely to require changes to the JIT as well, > but this is not the majority of the work > * Language changes, such as those proposed in RFCs, often require JIT > changes as well. But RFCs are not required to implement JIT changes > before voting, so this only adds overhead on accepted RFCs. This > represents a very small fraction of the work required on an RFC. > * Other changes don't usually need to care about the JIT > > Best Regards, > Arnaud To expand on this, the only times I really need to touch the JIT is when proposing language deprecations. Even when working on the Container/Offset RFC, the tweaking of the JIT was relatively straight-forward. Best regards, Gina P. Banyard
