Git proper has had rust code in it since 2.52, as an opt-in optional. 2.55 makes it opt out. 3.0 might make it required.

Yeah you can configure gh “wikis” to be freely editable but that’s not the default and most of them are not,

It is. Although it’s a hidden git repo with none of the GitHub tooling.

TFA literally notes that one if the key sha256 devs is a github employee and in favor of the transition.

And sha256 is in private preview at GitHub: https://github.com/bk2204/talk-rust-in-git/blob/dev/presenta...

Git does not use sparse files no, however in packs objects are delta-ified: any object can be either literal or a combination of literal segments and range copies from a base object, and that base object can be the same, recursively. So to resolve any object you need to jump around a fair bit in the pack file. The normal GC creates delta chain of length 10, aggressive defaults to 50, the maximum is 4095.

> "<-chan TYPE" is the receive end, "chan<- TYPE" is the send end, "chan TYPE" without an arrow can be used for either.

The problem is that there is pretty much just a subtyping relationship, when you convert a channel to a send or receive channel you don't get a different object, you just get the relevant subset of operations.

> There is no way to explicitly "close" the receive end.

And that's the root cause of half of more of the example issues in TFA. With the ability to close either end of the channel (and to handle closed receivers from the senders, obviously), most of the issues just go away (even more reliably so if that happens for you when the relevant end stops being used).

(2) has a bit more nuance to it: you can close channels… but the langage is designed for that to only be ok on single senders, a receiver can gracefully handle a closed channel (an iteration will just stop, a receive can use the 2-valued form to get the information), a sender will always straight up panic. Aka go channels are designed for fan-out.

And not closing channels is also considered idiomatic, per a tour of go:

> Channels aren't like files; you don't usually need to close them.

Also libwebp.

Getting to that is one of the reasons why people would kinda just grow apple seeds all over.

Plus they were not completely wasted, while not generally edible they’re fine for cider.

Heterozygosity and self-incompatibility are common to fruit trees in general, not specific to apples.

I think ancestral citruses (not the crosses) are the primary exception, as well as a few citrus hybrids which create clone seeds asexually.

> Outside of Granny Smith apples the ones you eat are mostly the results of mutations in the grown plants that we cut off and graft.

Honeycrisp is a chance seedling, though it stems from a horticultural crossbreeding effort it was grown from seed. And commercially useful sport mutations tend to come from popular chance seedlings to start with, since it is necessarily a more limited evolution of the basal cultivar, which needs to exist and in sufficient quantity that you’ll roll out useful mutations eventually (also useful is in the eye of the beholder as we can see with the red so-called delicious).