> Vale solves this by isolating threads' memory from each other (except in the case of mutexes or Seamless Concurrency). Given the whole point of threads is co

> Vale solves this by isolating threads' memory from each other (except in the case of mutexes or Seamless Concurrency). Given the whole point of threads is concurrency while sharing a memory space, and given we already have semantics on which data is thread local and how the ownership of heap memory should be handled, what's the point of that? To me it sounds like some people fail to understand how the complexity they are trying to pile onto C++ is slowly killing C++ due to the sheer volume of all the cognitive load they're trying to add.