3 ms·
Hmm, there's a distinct change of opinion by andrewrk from the linked issue (2022) to now https://github.com/ziglang/zig/issues/12064 https://github.com/ziglan
by kibibu 3y ago
Hmm, there's a distinct change of opinion by andrewrk from the linked issue (2022) to now
https://github.com/ziglang/zig/issues/12064 https://github.com/ziglang/zig/issues/12064 (July 2022):
> Hope you don't mind I'm going to reopen this issue because it concisely demonstrates a design flaw with result location semantics and I'm not ready to accept status quo as permanent due to aliasing issues like this.
Compare to a very closely related issue regarding destructing, which exhibits the same problem
https://github.com/ziglang/zig/issues/17283 https://github.com/ziglang/zig/issues/17283 September 2023):
> This is working as designed. Everybody was aware this behavior would be a consequence of destructuring and there is no plan to change it.