search for: inbonud

...t; At the same time, given that no memory access ever happens for a ZST, allocating >> a ZST (Box::new in Rust, think of it like new in C++) does not actually allocate >> any memory, it just returns an integer (sufficiently aligned) cast to a pointer. > > OK, but why not emit non-inbonuds GEPs instead? They do not come with > the problems you have now, or maybe I misunderstand. The problem is statically figuring out whether it should be inbounds or non-inbounds. When we have code like `&x[n]`, this might be an offset-by-0 in an empty slice and hence fall into the scope of...

Hi Johannes, > Now that reasoning works from a conceptual standpoint only for > non-inbounds GEPs, I think. From a practical standpoint my above > description will probably make sure everything works out just fine (see > also my rephrased answer down below!). I say this because I think the > following lang-ref passage makes sure everything, not only memory > accesses, involving