24 ms·
I meant slow as in the time it takes for the committees approval. What exactly does this language solve in Google’s problem domain that can’t be enforced throu
by pipeline_peak 4y ago
I meant slow as in the time it takes for the committees approval.
What exactly does this language solve in Google’s problem domain that can’t be enforced through guidelines?
- shagie 4y agoRather than enforcing the style guide ( https://google.github.io/styleguide/cppguide.html https://google.github.io/styleguide/cppguide.html ) through code reviews and code review tools, the language itself encourages the developer to write better code than they would have if writing C++. The Google C++ style guide is longer than the Carbon language design (though I will note a large number of sections that are "TODO"). (working from guesswork here) Given the codebase that Google currently has in C++, the amount of effort to continue enforcing those style guides through human "this needs to change before I can approve it" to (in Google's eyes) more reasonable code with Carbon ultimately results in less developer time being spent reviewing style guide issues. At that scale, this may become a significant savings even when taking into account creating a new language.
- pipeline_peak 4y agoIt’s likely smaller than the style guide because it was just introduced. Either way that’s such a loose comparison. I’m aware a language that enforces better coding styles is more efficient, I’m asking how and why does Carbon do this.
- shagie 4y agoIt has been a long time since I did work in C++, and I recall a number of foot-guns in the language. Reading the design document for Carbon and looking at the samples, it appears that many of these are not as easy to access. Things such as "not using the preprocessor for meta programming" by itself is a significant advantage.