Aria Desires

Ideally this would use the same solution we pick for https://github.com/axodotdev/oranda/pull/507

I would especially appreciate if someone could properly write down in one of our primary sources (nomicon, trpl, or reference) what on earth happens with double-panics and panic-in-destructors. I feel...

Note the nomicon discusses some stuff: * https://doc.rust-lang.org/nightly/nomicon/destructors.html * https://doc.rust-lang.org/nightly/nomicon/leaking.html But these docs are getting *extremely* long in the tooth (ManuallyDrop exists now, for instance).

The most important thing, imo, is that the "fixed" scoped_thread pattern works: ```rust fn main() { let state_to_get_borrowed_by_other_thread = ...; scope(|spawner| { for i in 0..10 { let borrow =...

Arguably you can still "allow" this along similar lines of how I suggested permitting double-drop: implementors of Drop that are properly kept in local vars are guaranteed that their destructor...

I don't think catch_unwind is notably different from a destructor in this case?

no its for binary_heap’s heapify operation (in case cmp panics)

Hey! We specifically do give the `packages: write` permission to custom-publish-jobs (as opposed to custom-build-jobs). Docker images are really annoying because nothing fundamentally prevents building and publishing being split up......

for the record, the magic incantation to avoid quotes is `|safe`: https://github.com/axodotdev/cargo-dist/blob/9be2d30c4ac6ca58c0aa1cdb8510358121da569b/cargo-dist/templates/ci/github_ci.yml.j2#L345 but yeah we avoid using that unless absolutely necessary because ✨reliability

So! while you were gone we *just* landed a big new prototype feature for "generic" builds with all the gorey details of cflags and whatnot, so cargo-dist is More Than...