David Allsopp

> I do not understand why `ocamlc.opt` has to depend on `stdlib/libasmrun.$(A)` whereas this file does not actually appear on the command-line? `stdlib/libasmrun.$(A)` will be linked by ocamlopt to create...

Any program compiled with `ocamlopt` does have a direct, real dependency on `libasmrun.a` (as in, the code in `libasmrun.a` will appear in that program), it's just that it's not part...

Some work started on this in #11369 - I'm expecting resurrecting the MSVC port in 5.x will be a good opportunity to wind the rest of the codebase forwards (and...

> A nerd-sniping bug for sure. Oh yeah 🤓 > Is this what you had in mind with your plan (3), or something simpler? I'd started down the line of...

Sorry, I had managed to forget about this. I disappeared down another slight rabbit hole with this - in particular, on my machine while I see the speed-up in the...

OK, I've opened the simplest PR just to ensure that we there's something - it's up to you if you want to have a go at the spill optimisations, @gasche?

@c-cube - I'd been mucking around with ideas based around potentially blitting to the wrong buffer, yes... just running out of time 🙂

It's a very reasonable 2¢, @nojb! The main thing with a lot of the work towards this is that there are a _lot_ of strands of work which pull in...

Just to link it in, I think the original issue was addressed in 2016 in #514

See https://github.com/ocaml/opam/issues/4519#issuecomment-868445795