Jakob Degen

> is it even true that the layout is fixed? I can totally imagine a compiler optimization that e.g. uses different layout for different local variables of the same type,...

> The pointer may not be computed explicitly, but perhaps there is still some roundabout way to get it via unsafe code. Trying to bound the behaviour of unsafe code...

@afetisov none of those things don't apply just as much to `size_of`. Is your claim that providing that was a mistake too? > exposing offsets means that the layout is...

The right solution here for the unsized case is to stop representing `&move` arguments in MIR with an `Operand::Move`. `Operand::Move` is also very clear about the fact that it makes...

I'm going to start work on this. I'm not sure how it will go yet, but I'll do what I can and open a draft PR as soon as it...

This seems maybe related to but not obviously the same as #581 and #582

Ah, there was a bug in my previous testing. This does not require git to reproduce, and making the same commits in a normal sl repo shows this behavior too...

This reproduces similarly with explicit `"ancestors(.)"` and `"ancestors($(sl whereami))"`

Oh, I'm realizing that the comments from lang team members are two years old and so may be outdated. Anyway, I've nominated for discussion by the council [here](https://rust-lang.zulipchat.com/#narrow/stream/392734-council/topic/Nominating.20issue.20for.20discussion/near/384361260) , I'm...

Updated to require >= 2/3. I think asking the affected teams if this makes sense to them seems reasonable. I don't know where the best place to hold such an...