This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.
hyperhello [3 hidden]5 mins ago
This comment was obviously written by Opus 3.8. Not even 4.0.
thinkafter [3 hidden]5 mins ago
I’m not sure about copy but the UI seems designed to look like an AI response which is certainly a choice
ternaryoperator [3 hidden]5 mins ago
It's great to have it all spec'd out. However, I think specs like this suffer the same fate as war plans: they get modified quickly as soon as implementation begins. Nonetheless, it's good to have a clear idea of where you're headed. I just wouldn't call it "Final."
ronsor [3 hidden]5 mins ago
Before I read this, what is there about C3 [0] you don't like?
This doesnt seems to be meaningfully different from Rust.
> does not require tracing garbage collection
Just call it garbage collection.
(Applies in two ways: if you think that garbage collection subsumes reference counting then this language doesn’t require garbage collection in the sense that it also doesn’t require reference counting; if you think that garbage collection does not subsume reference counting then there’s no point in saying three words when you can say two.)
drgo [3 hidden]5 mins ago
reads more like a Wishlist rather than actual implementable specs.
nextaccountic [3 hidden]5 mins ago
every spec is implementable
some just delegate more or less to the implementation
nextaccountic [3 hidden]5 mins ago
that said, the borrowing part is incredibly short on details
i read trying to assess if it's more or less expressible than rust's current nll or the future polonius and honestly there's nothing there
woodruffw [3 hidden]5 mins ago
Another one?
yoklov [3 hidden]5 mins ago
This is certainly copying off Rust's homework...
Fordec [3 hidden]5 mins ago
Who copied off Haskells homework, so here we are.
irishcoffee [3 hidden]5 mins ago
And cloudflare still somehow shipped a rust binary that crashed half the internet.
[0] https://c3-lang.org
> does not require tracing garbage collection
Just call it garbage collection.
(Applies in two ways: if you think that garbage collection subsumes reference counting then this language doesn’t require garbage collection in the sense that it also doesn’t require reference counting; if you think that garbage collection does not subsume reference counting then there’s no point in saying three words when you can say two.)
some just delegate more or less to the implementation
i read trying to assess if it's more or less expressible than rust's current nll or the future polonius and honestly there's nothing there