I don’t think the memory safety guarantees of Rust could be expressed in the syntax of a language like C or Go.
I don’t think that’s the case, somehow most ML derived languages ended up with stronger type system and cleaner syntax.
I don’t think the memory safety guarantees of Rust could be expressed in the syntax of a language like C or Go.
I don’t think that’s the case, somehow most ML derived languages ended up with stronger type system and cleaner syntax.
That said, personally I’ve always found the gesture navigation very intuitive.
Definitely a weird thing to advertise.
That's one hell of a language!
While there are some new rules regarding arguments naming, the new syntax doesn’t feel more complex than the default lambda syntax.
So all in all I would say the most horrifying thing here is the fact that the language allows such extensions in the first place ;)
"A new type of interpreter has been added to CPython. It uses tail calls between small C functions that implement individual Python opcodes, rather than one large C case statement."
[0] https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-...
Notably, this is not the case. C++ std::vector is specialised for bools to pack bits into words, causing an untold array (heh) of headaches.
And "wasteful" is doing a lot of lifting here. In terms of memory usage? Yes. In terms of CPU? The other way around.
That depends on your architecture and access pattern. In case of sequential access, packed bools may perform better due to arithmetic being usually way cheaper than memory operations.