Hi! Kind of both. Even though Valen reuses 90% of the Vale compiler, its approach (Rust interop, borrow checking with mutable aliasing, etc.) is so different that it really needed a new name.
replyAlso, I really like where Vale ended up, Vale's generational references + region borrowing was a truly weird and unusual memory safety blend. I didn't want that combination to be lost to time, so I wanted "Vale" to keep referring to that.
A bit sad to see Vale archived. Have you written a final post on it (lessons learned, the good and the bad, fundamental strengths and weaknesses, future research needed, all that)?
replyNo, but that's a great idea. Vale definitely taught me a lot about languages and architecture. I might do that...
replyThank you. Your writings on memory safety and other similar topics is appreciated, and the work you are doing seems to point in a very interesting direction that I am sure will bring a new breakthrough similar to what Rust (or, more accurately, Cyclone) brought. Very interested in what will percolate in Mojo and Ante too.
reply