Patrick Walton

This is implemented in https://github.com/pcwalton/cxx-async

Sounds great!

I've investigated this problem. The link error is caused by `literal_pointers,no_dead_strip`. For sections with those flags, Apple's `ld` takes a special "literal pointers" path that doesn't do all the relocations...

@kvark Why isn't `lazy_static` good enough for your needs?

Oh, I'm not sure we need downstream crates to use `lazy_static!` *explicitly*. I think `rust-objc` could use it internally. I'm experimenting with a PR now…

Sorry to be this way, but I'm pretty worried about adding more undefined behavior to Rust to support a niche project like CHERI. Rust UB is already very hard to...

To address that FAQ issue, I don't think that it's frustrating at all for programmers that provenance is vaguely broken. I think it's frustrating for *compiler writers* and people who...

To be more concrete, I'd prefer we just use something like PNVI-ae-udi. Maybe we could tighten things up a little, but that seems like a good place to start.

Well, to be honest, the problem *is* that pointer provenance bugs are empirically very rare. Which is why it hasn't been properly solved in C and C++ to begin with....

I guess what I'm arguing here is that a lot of thought needs to be given to how this can become opt-in, because it seems to me that strict provenance...