knuckleheads

If others find beauty in something, should I not want to also try and see it?

Some things take time to learn to enjoy. I've bounced off things in the past several times before I started to really enjoy them later on. I'd like to think my experience with media is not just a random walk through whatever is in front of me and that I can direct that experience, at least a bit.

I’ve tried both! Both fun in their own ways but they never caught me long term. Sausage rolls was fun but it just got too hard.

I am generally not a fan of Sokoban puzzles, but I told myself that Order was the best chance to fix that so I’ve been forcing myself to play it. I don’t find myself actively wanting to sit down and play it, the puzzles don’t attract me that way, but once I do, I’ll play for about five hours at once. Great game.

It’s a neat idea. My impression is that it would go against the grain of the compiler currently. The rmeta file and lots of the other rust outputs aren’t meant to be that stable that it could be portable like that. I’ll certainly mess around with this some and see if anything comes of it though!

I would be very curious to know how that test went please!

Yes, if you mostly have no extra cores already or if you have very wide unrelated deps, this mostly does nothing. Typically, this is not the case though so there is some good perf gains.

I wanted everything in one repo and this worked well enough. For presenting to rust compiler team I forked the repos in question and made branches for review with the patches.

Yes it's a pretty well thought out policy. It feels bad for someone to put in a month of work and have their code ultimately rejected, but if an llm does something sloppy with some light guidance in a few days, then great, experiment with some weird stuff and see what happens, then once you know it probably should work, go in for that month of work and make it happen.

(Copying and pasting from what I posted in rust zulip)

There is an .early-rmeta file that is generated that contains the result of type checking the outer part of the functions (arguments, returns) that is then passed down to all the other dependencies that can use it and get a "headstart" on their work. -Zearly-metadata is the flag for Rustc here to turn that on. It also needed to learn how to swap the real metadata in for the early stuff that it was previously using, once the real stuff showed up.

Rustc needs to be able to pause and resume at certain points and Cargo needs to be know how to look for and react to that, which is what -Zheadstart does for Cargo. So there's some changes job_queue that happen to there. I haven't checked this directly yet, but my understanding is that it doesn't kill the process, it just has it sit and wait, which normally would occupy a slot, but doesn't any longer. ---

So not a cache, just being able to pause and start work and better utilize the available slots.

Talking with them presently! This specific set of changes won't get in (LLM written, little to no thinking through of the broader design), but I am hoping something like it shows up sometime.