Google Launches Carbon, an Experimental Replacement for C++
1–10 of 243 posts
Re: Google Launches Carbon, an Experimental Replacement for C++
#2It’s clear that the value promise of Carbon is to make it attractive to port existing C++ applications to it.
But how this is accomplished, article does not go into detail in this. Is there going to be ABI compatibility with C++? What are the features that make Carbon a better porting target than Rust?
Re: Google Launches Carbon, an Experimental Replacement for C++
#3Previous discussion: https://news.ycombinator.com/item?id=32151609
Re: Google Launches Carbon, an Experimental Replacement for C++
#4I’m a big fan of ‘var’ and ‘let’ in Swift. Easier to identify mutable vs immutable variables. I believe Carbon uses the same convention?
https://github.com/carbon-language/carbon-lang
Helps with quick auto-completion, and someday when I get to dictate code, fewer mistakes.
Re: Google Launches Carbon, an Experimental Replacement for C++
#5 var r : i32;
How is this any better than int32_t r;
?
all I see is additional, unnecessary keyword to type.Re: Google Launches Carbon, an Experimental Replacement for C++
#6If you cannot write a naive "carbon" compiler as a small team or even an normally skilled individual in a reasonable amount of time and effort, same abomination than c++ syntax, next.
Re: Google Launches Carbon, an Experimental Replacement for C++
#7Looks like there's no need to wait for Unreal Verse anymore
Re: Google Launches Carbon, an Experimental Replacement for C++
#8var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
You type about the same number of characters. Now imagine you wanted to declare the value to be immutable.
Re: Google Launches Carbon, an Experimental Replacement for C++
#9I've been seeing a lot of references to this across youtube, reddit etc for a new experimental language. Is google putting their full weight behind this like Go or is the virality just incidental?
Re: Google Launches Carbon, an Experimental Replacement for C++
#10var r : i32; How is this any better than int32_t r; ? all I see is additional, unnecessary keyword to type.
I think by using `var` keyword you have the potential to inherit the type without changing too much the syntax, in rust you could omit the type if the compiler can inherit the type, that saves you a lot of typing in the future, but you could argue that it makes harder to read the source code without any tool.