We also discovered that they (Generational References) enable Vale to have complete memory safety, something no native language has been able to achieve.
@macleod this reads like #Vale hopes to be the #Rust killer, but you do realize that the Rust borrow checker also protects against data races in multithreaded code, right?
I don't see anything in the pitch to do with multithreading
I'm also unclear on the "complete memory safety" claim given the extensive discussion of overriding the generation check. The "no native language" claim seems questionable too
@igrok@macleod My disappointment with generational references, handles, and similar pointer hardening is that they only protect safety, but not help correctness. You can still have dangling references and use after free. It's mitigating bugs instead of preventing them.
@kornel@igrok Multithreading will be supported with their concurrency models, in fact it's wrapped in a single keyword "parallel" that prevents data races.
Add comment