3 ms·
> If you are interested in helping solve any of these problems, please reach out! Coincidentally, we're working on these problems with Vale [0] by obviating th
by verdagon 5y ago
> If you are interested in helping solve any of these problems, please reach out!
Coincidentally, we're working on these problems with Vale [0] by obviating the need for unsafe, while still having single ownership's performance benefits, by taking generational indices (a common Rust/C++ technique) and building them into the language itself, and by moving borrow checking to the region level instead of the object level [1].
Time will tell if it works out!
[0] https://vale.dev/ https://vale.dev/
[1] https://verdagon.dev/blog/seamless-fearless-structured-concurrency https://verdagon.dev/blog/seamless-fearless-structured-concu...
- zozbot234 5y agoMany PL folks are now looking into ways to generalize Rust's borrow checking approach. Even the Rust community is getting into this kind of stuff with the GhostCell proposal and its many variations. It remains to be seen how such extensions and generalizations might be adopted in a way that's reasonably intuitive and ergonomic.