CobaltC – The Successor to C?

13 points - today at 2:26 AM

Source

Comments

ethin today at 3:49 AM
This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.
rurban today at 4:43 AM
Unsafe identifiers, prone to homoglyph attacks. No TR39 provisions. Worse than rust or Java. https://strawberry9.github.io/the-wrong-memory/Appendix_06.h...
ronsor today at 3:08 AM
Before I read this, what is there about C3 [0] you don't like?

[0] https://c3-lang.org

ternaryoperator today at 4:04 AM
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."
pizlonator today at 3:44 AM
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 today at 2:42 AM
reads more like a Wishlist rather than actual implementable specs.
yoklov today at 3:12 AM
This is certainly copying off Rust's homework...
woodruffw today at 4:33 AM
Another one?