Hacker News new | past | comments | ask | show | jobs | submit login

> 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.




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.


My apologies; I misread your original statement to imply that unsafe would necessarily imply undefined behavior.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: