Get the latest tech news

Group Borrowing: Zero-cost memory safety with fewer restrictions

If you've read my blog before, you know that memory safety is a huge unsolved problem, and that there's a vast unexplored space between the various memory safety models. The discerning eye can infer that we're starting to see the lines blur between these seemingly unrelated memory safety approaches.

I'll try to explain the approach as simply as possible, but if you have any questions, Nick can be found in the Mojo server(username nick.sm), or feel free to ask me in the r/vale subreddit or the Vale discord's #languages channel. The borrow checker has long been known to reject programs that are actually safe, causing you to add and change code to satisfy its constraints. Or using our more familiar terms: the Ring could be independently destroyed (such as via a remove or append call on the ArrayList), so it's in a child group, so the compiler shouldn't let us use our reference after the damage method.

Get the Android app