Diggory Blake

Overall I like this idea for Rust, but it seems incompatible for C interop. It's pretty common in C APIs to use an integer as a "user-data" field intended to...

> I feel like it's very plausible to define some sort of pointer-int union without messing with ABI for "this is a pointer, the API is lying" But then you...

> (This assume GetWindowLongPtrW returns a type that can carry provenance, like *mut c_void.) It does not, it returns an integer, but presumably you are suggesting redefining the function such...

@arichardson presumably that's because `intptr_t` is typedef'd to some special intrinsic type that is lowered to a pointer only for CHERI? That's an additional incompatibility then, because Rust's `isize` is...

I think my concerns with C interop basically boil down to this: Rust might need a way to interoperate with the [PNVI-ae-udi](http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2676.pdf) model (assuming that is what C goes with)...

@RalfJung surely if one were determined to make XOR lists work, it would be better to define an XOR operation on pointers (ie. that XORs the address part and performs...

Crazy idea: what if we defined optimization levels according to the model which the corresponding optimization passes were compatible with? So for example, the highest optimization level would run all...

Right, I think we'd still want to be clear that (assuming this all goes through) we think the strict provenance model is the future - that it's something that all...

This is likely blocked on these issues in winit: https://github.com/tomaka/winit/issues/276 https://github.com/tomaka/winit/issues/266 https://github.com/tomaka/winit/issues/231

Can't RLS do a best-effort thing here? Rename the uses outside macros, and provide a list of the places which RLS could not rename?