Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Internal use of unsafe requires securing the safe code at the module boundary

Not even that, because you can pass data structures from unsafe code at arbitrary depth.





If the goal is to make a safe abstraction, which is what I'm talking about, proper use of visibility and safe code at the module boundary encapsulates the unsafe code soundly.

You seem to be talking either about improper encapsulation or unsafe that is intended to be exported and used unsafely. Or perhaps some method that is not sound according to the language.




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

Search: