Happy new year to all my friends and followers. I hope you achieved all you set out to in 2019 and that the next twelve months are even more than you could have hoped for.
Aha righty, yes. rustdoc embeds the font I believe. So it sounds like a patch to mdbook is needed, then a new release will mean new toolchain docs have that fixed. Do you think you're up to investigating writing that patch?
Phew, I might have struggled a *LOT* with yesterday's #adventofcode but at least I know how to wrangle a network of intcode VMs with relative ease. Timesliced computing FTW!
I guess to make that work, we'd need (a) to work out if we're allowed to distribute those fonts, and (b) have a variant of the doc generation which embedded local copies. Which documentation is trying to load remote fonts?
I have stocked my fridge with soft tofu tubes, a bunch of spring onions, some other veg, and I have a bunch of other bits ready for tomorrow's Kimchi Tofu Stew cooking effort @codethink -- I hope the Codethings bellies are ready.
I bought a pack of pre-cooked pre-peeled because it's less likely to burn my fingers -- but you are *quite right* -- just off the fire (or out of the oven) is best.
Today's #adventofcode really kicked my arse. @ericwastl writes some fiendish puzzles from time to time. This one takes way too long for my solution to run (3+ seconds) so I'm going to have to get my optimisation hat on.
some languages model open slices differently to fixed length slices. Eg in rust the difference between [T] and [T; n] but this isn't used often and is rarely properly useful since indices are usually either zero or some variable which can't be compile-time checked anyway.