News for hackers. Stuff that matters.
Re:Carbon Language: An experimental successor to C++ by adev_ on Tuesday July 19, 2022 @07:04PM (#32159127)
> C++ has virtually zero tooling and the committee is not interested in ever working on that

This sentence makes no sense at all:

1 - Tooling does not stop to the build systems

2 - The tooling set in C++ (and C) has been built over decades. It is indeed not a single shiny CLI cargo-style but it several order of magnitude bigger and more powerful than anything you will ever find in any other programming language: memtracers, profilers, thread sanitizers, debuggers, disassemblers, static analyzers, packages managers, bindings generators, ABI checkers, crash analyzers, loggers and I am sure I forget still many others.

Re:Carbon Language: An experimental successor to C++ by fouronnes3 on Wednesday July 20, 2022 @01:28AM (#32161795)
Yeah what I meant was build system tooling, sorry for the approximation.
Re:Carbon Language: An experimental successor to C++ by flohofwoe on Wednesday July 20, 2022 @01:58AM (#32161981)
Most of the tools you mention work below the language level, and thus work automatically for non-C/C++ languages too (or at least LLVM-based languages).
Re:Carbon Language: An experimental successor to C++ by adev_ on Wednesday July 20, 2022 @05:31AM (#32163343)
They do work below the language level but have been generally explicitly made for C and C++ programs. e.g abi-compliance-checker

The other languages benefit of them currently because they leverage LLVM (also made in C++), because their interpreter/VM are made directly in C.

How is it already ? Standing on the shoulders of giants ? :)