Discussion
RE: https://thicc.horse/@and/117293289884500133
Like they're closing off our escape routes one by one
Looks like GCC officially has claude commits landing starting here. And they've been landing steadily in the repo.
https://gcc.gnu.org/cgit/gcc/commit/?id=be1da01067c898a3e3979bfb1edd05f115ab2e3e
Notes on previous post:
1. Although the safety guarantees in Rust are obviously most of the point, a specific place where I think we could modify things without making our lives worse is by rethinking the approach to multithreading. What if the "only one mutable pointer at a time" rule were more like a "two threads may not hold pointers to a piece of data at the same time" rule? What would that do?
2. C is neither a systems language nor especially easy to implement. Don't @ me
@mcc Kotlin Native did this in the beginning, there was no shared memory, you had to "freeze" object subtrees and send them around. it was very difficult to use, but it could be that the type system was just not there
@charlag Kotlin is a really really interesting language in so many ways but I would not describe it as "simple"
Install Fedizen
Get the full app experience
This may sound like a non sequitur:
I'm interested in someone developing something which takes the "ownership" idea that makes it possible for Rust to do exact pauseless memory management and relaxes it, either to increase programmer workload or to weaken safety guarantees, in such a way as to make a compact independent reimplementation easier. I think at some point we will need a systems language which is as easy to implement as Python 2.