Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Why introduce `std::launder` rather than have the compiler take care of it?. Parent comment
> if you allocate a new object in the storage of the old one, you cannot access the new object through pointers to the old
Which implies the UB happens in the caller.
The access in the caller -- `return f.x` -- is not through a pointer.
> if you allocate a new object in the storage of the old one, you cannot access the new object through pointers to the old
Which implies the UB happens in the caller.