I’m not sure about copy but the UI seems designed to look like an AI response which is certainly a choice

This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.

This doesnt seems to be meaningfully different from Rust.&gt; does not require tracing garbage collectionJust 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.)

To clarify: C3 has fixed sized ints. Maybe the parent poster doesn’t like their names, but they are fixed sized, as follows:<pre><code> Name Size Signed
 bool 1 no
 ichar 8 yes
 char 8 no
 short 16 yes
 ushort 16 no
 int 32 yes
 uint 32 no
 long 64 yes
 ulong 64 no
 int128 128 yes
 uint128 128 no
</code></pre>
Source: <a href="https:&#x2F;&#x2F;c3-lang.org&#x2F;language-overview&#x2F;types&#x2F;#integer-types" rel="nofollow">https:&#x2F;&#x2F;c3-lang.org&#x2F;language-overview&#x2F;types&#x2F;#integer-types</a>

C3 is an embarrassing mess regarding integer types and sizes, missing C99&#x27;s stdint.h defs, for example.

Before I read this, what is there about C3 [0] you don&#x27;t like?[0] <a href="https:&#x2F;&#x2F;c3-lang.org" rel="nofollow">https:&#x2F;&#x2F;c3-lang.org</a>

It&#x27;s great to have it all spec&#x27;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&#x27;s good to have a clear idea of where you&#x27;re headed. I just wouldn&#x27;t call it &quot;Final.&quot;

Unsafe identifiers, prone to homoglyph attacks. No TR39 provisions. Worse than rust or Java. <a href="https:&#x2F;&#x2F;strawberry9.github.io&#x2F;the-wrong-memory&#x2F;Appendix_06.html#section-6" rel="nofollow">https:&#x2F;&#x2F;strawberry9.github.io&#x2F;the-wrong-memory&#x2F;Appendix_06.h...</a>

that said, the borrowing part is incredibly short on detailsi read trying to assess if it&#x27;s more or less expressible than rust&#x27;s current nll or the future polonius and honestly there&#x27;s nothing there

every spec is implementablesome just delegate more or less to the implementation

reads more like a Wishlist rather than actual implementable specs.

And cloudflare still somehow shipped a rust binary that crashed half the internet.

Who copied off Haskells homework, so here we are.

This is certainly copying off Rust&#x27;s homework...

Yes, but remember is the last appendix to a book, and book provides the context for this appendix. So yes, in that sense, it&#x27;s just another one attempting to address the memory-safety issues of C. At least this one uses C like syntax and doesn&#x27;t require C programmers to learn some alien syntax. Of course, this is just a spec, Rust is well and truly live in the environment. The book is more interesting than the spec.

Odin&#x27;s turn to be &quot;the sucessor of C&quot; is due this month

CobaltC – The Successor to C?