They also allow reviewing commits individually, which is very frustrating to do without dedicated support (unless you devolve back to mailing list patch stacks).

Stacked PRs are a development method, for managing changes which are separate but dependent on one another (stacked).

The two are orthogonal they can be used together or independently (or not at all).

And from an older NASA explanation: https://www.nasa.gov/news-release/nasa-shares-orion-heat-shi...

> Engineers already are assembling and integrating the Orion spacecraft for Artemis III based on lessons learned from Artemis I and implementing enhancements to how heat shields for crewed returns from lunar landing missions are manufactured to achieve uniformity and consistent permeability.

The big recess above the pins is what encases the button of the charger and provides grounding if it includes metal strips. Assuming the charger itself has a metal button.

In the EU a grounded cable has been the default forever (I have a grounded cable from my 2010 MBP which I use as travel cable for my 2021 MBP)

That is essentially the motivation, primarily in the context of FFI where matching C's union behaviour using transmute is tricky and error-prone.

That has led to a significant number of people switching over from openai, or at least stating they were going to do so.

You can’t downvote submissions. That’s literally not a feature of the site. You can only flag submissions, if you have more that 31 karma.

A broken commit usually compiles, if you don’t even compile before committing you should go back to school.

> If you feel the need to rebase to squash one-liner fixups into the commits they fix then that's a more subtle tradeoff and there are reasonable arguments. But squashing your whole PR for the sake of that

It would really have helped if you’d stated upfront that you can’t read.

Low level strong correctness was absolutely a novel part. In fact it’s exactly why many people glommed onto early rust, and why it was lowered on the stack.

Although learnability and weirdness budgets were also extremely novel in low level contexts which had been subsumed by C and C++.

> horrors in C++

Yes, horrors in C++. Half baked jerry-rigged and barely usable nonsense. Not an industrial strength langage with a reliable type system and a strong focus on safety through types.

When did OCaml get affine types? Or unique references?

Why would there be? Go’s assembly might be lacking ways to make them optimally efficient, but that’s probably a given either way without an optimizing compiler backend.

isize is the type for signed memory offsets, fsize is completely nonsensical.

The tendency was probably always there given the serial lying about self driving started circa 2015, or the weird ego trip of ousting the founders and getting himself called co-founder, but if we’re looking for a point event the removal of his long time PA in 2014 still stands out to me.

Length + pointer is a record string, a pascal string has the length at the head of the buffer, behind the pointer.