CobaltC – The Successor to C?
strawberry9.github.io
CobaltC – The Successor to C?
1–10 of 24 posts
Re: CobaltC – The Successor to C?
#2reads more like a Wishlist rather than actual implementable specs.
Re: CobaltC – The Successor to C?
#3Before I read this, what is there about C3 [0] you don't like?
Re: CobaltC – The Successor to C?
#4This is certainly copying off Rust's homework...
Re: CobaltC – The Successor to C?
#5reads more like a Wishlist rather than actual implementable specs.
every spec is implementable
some just delegate more or less to the implementation
Re: CobaltC – The Successor to C?
#6reads more like a Wishlist rather than actual implementable specs.
every spec is implementable some just delegate more or less to the implementation
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
Re: CobaltC – The Successor to C?
#7This is certainly copying off Rust's homework...
Who copied off Haskells homework, so here we are.
Re: CobaltC – The Successor to C?
#8Before I read this, what is there about C3 [0] you don't like? [0] https://c3-lang.org
C3 is an embarrassing mess regarding integer types and sizes, missing C99's stdint.h defs, for example.
Re: CobaltC – The Successor to C?
#9This 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.)