So how do you guarantee that the caller invariants are upheld, e.g., that the un... | Hacker News

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

login

fluffything on July 16, 2019 | parent | context | favorite | on: Ownership and Borrowing in D

So how do you guarantee that the caller invariants are upheld, e.g., that the unannotated code does not leak a pointer to a different thread, etc. ?

WalterBright on July 16, 2019 | [–]

> So how do you guarantee that the caller invariants are upheld

You can't, you have to trust the user. That's why one tries to minimize calling non-@live code.

mntmoss on July 16, 2019 | [–]

How do you do that in unsafe Rust?

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact