Even with a single thread you need to ensure that the object you are accessing, ... | Hacker News

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

		codedokode 82 days ago \| parent \| context \| favorite \| on: Group Borrowing: Zero-cost memory safety with fewe... Even with a single thread you need to ensure that the object you are accessing, still exists and was not freed.

wavemode 82 days ago [–]

If you're talking about stack objects, that's what lifetimes are for.

If you're talking about heap, you can accomplish that by restricting that the references can't be used to free or invalidate the memory. But you could still allow them to be mutable.

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