CobaltC – The Successor to C?
9 points - today at 2:26 AM
SourceThis is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.
thinkafter
today at 3:57 AM
I’m not sure about copy but the UI seems designed to look like an AI response which is certainly a choice
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.)
Before I read this, what is there about C3 [0] you don't like?
[0] https://c3-lang.org
jjtheblunt
today at 3:34 AM
C3 is an embarrassing mess regarding integer types and sizes, missing C99's stdint.h defs, for example.
strenholme
today at 3:55 AM
To clarify: C3 has fixed sized ints. Maybe the parent poster doesn’t like their names, but they are fixed sized, as follows:
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
Source:
https://c3-lang.org/language-overview/types/#integer-types
reads more like a Wishlist rather than actual implementable specs.
nextaccountic
today at 3:15 AM
every spec is implementable
some just delegate more or less to the implementation
nextaccountic
today at 3:18 AM
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
This is certainly copying off Rust's homework...
Who copied off Haskells homework, so here we are.
irishcoffee
today at 3:45 AM
And cloudflare still somehow shipped a rust binary that crashed half the internet.