News for hackers. Stuff that matters.
Re:Stacked Borrows: An Aliasing Model for Rust by kd5bjo on Sunday February 09, 2020 @06:27AM (#22281593)
> a demonstration that any program in the hypothetical dialect that can invoke undefined behaviour either uses `unsafe` or is rejected by the borrow checker.

This isn’t quite what they’re doing here. They’re trying to define what guarantees the compiler should make about its treatment of unsafe code to strike a balance between usability and the ability of the compiler to optimize.

Re:Stacked Borrows: An Aliasing Model for Rust by mjw1007 on Sunday February 09, 2020 @07:00AM (#22281696)
Sure, but we want to be sure that the chosen model fits in correctly with the borrow checker. That's the part I was interested in.
Re:Stacked Borrows: An Aliasing Model for Rust by kd5bjo on Sunday February 09, 2020 @08:58AM (#22282112)
My apologies; I misread your original statement to imply that unsafe would necessarily imply undefined behavior.