Val, a high-level systems programming language
I might actually be more excited about Val as a C++ successor than I am about Herb Sutter&#x27;s excellent CppFront...  Admittedly, all I know about it is from the two presentations below. But, from what I can tell...<p>Statically compiled. Statically typed. Interops with C++. Memory safe. Typesafe. Data-race-free.<p>The elevator pitch I give when describing it goes like this:  Imagine you were starting a new C++ project and didn&#x27;t really care about performance (spoiler: perf comes back in the end). So, you decide to not bother using pointers or references anywhere.  You just pass by value, return by value everywhere, all day long.  If you ignored the obvious perf problems of passing around maps of vectors of objects by value, wouldn&#x27;t it be nice?  you don&#x27;t have to worry about side effects or data races or anything. And yet, the data is not immutable. You can go ahead and mutate it all you want worry-free because the data is all completely local to your function.<p>Well, turns out the Val folks have figured out that by eliminating pointers and references from the language, the can get the compiler to automatically pass-by-const-reference and return-value-optimization under the hood such that it preserves both the performance and the semantics that you want at the same time.<p>Val: A Safe Language to Interoperate with C++ - Dimitri Racordon - CppCon 2022 <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ws-Z8xKbP4w">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ws-Z8xKbP4w</a><p><a href="https:&#x2F;&#x2F;cppcast.com&#x2F;val-and-mutable-value-semantics&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;cppcast.com&#x2F;val-and-mutable-value-semantics&#x2F;</a>