Connor Horman
Connor Horman
> I am just slightly concerned about this being an irreversible loss of optimization potential that we might regret later FTR, speaking right now as one of the main developers...
Indeed - it is not the intent of the RFC to require that arbitrary code remain valid in the presence of alised Box values, such a thing would be a...
So, elaborating on `Allocator`s in the Motivation section got me thinking. How does `GlobalAlloc` play in. Would `GlobalAlloc` not suffer similar issues if you wrote the allocator in Rust?
Link check errors are intentional in bea8b9d - I link to sections from #1618 and omitted the footnot references so it can be reverted when #1618 is merged.
> Can we move these rules into those chapters (and avoid any duplication with things that are already there)? We still have to define what a byte is, which is...
Need to figure out how to disentangle the aggregate representation rules to move them into a separate chapter.
@rustbot ready
Just talked about this on the Community Discord, apparently there is one guarantee this makes that is "new". Namely, it guarantees that wide pointers are represented like some repr(Rust) struct...
> We have never defined what Rust's concept of a "byte" is. Uninitialized memory is a thing (though AFAIK this was never explicitly FCP'd either), provenance is a thing, but...
Yes, I just haven't had much time to work on it.