Full C++ interop has always been my primary design goal, I will remain a hobby project with orders of magnitude fewer resources, but from now on whenever someone asks me "but why?!" I will be able to point at Carbon.
Carbon, a successor language to C++ was announced at @CppNorth today by @chandlerc1024.
I'm very excited about this project's potential. You can learn more about Carbon and get involved on GitHub.
https://t.co/p4UIBB6Irx
This is interesting — a compiler/runtime that makes almost all standard C/C++ code completely memory safe. The performance overhead is not negligible, but there are plenty of cases where “rewrite it in rust” still isn’t a practical solution.
As a person who programs in Rust since 2016 I can tell you that Rust is a very safe, unergonomic language with annoying community and atrocious syntax. Which is somehow surprisingly miles better than modern C++.
somethings really wrong guys, im writing C++ and actually having fun. someone better call a psychologist because i'm pretty sure this is stockholm syndrome
We lost a titan of programming languages, programming methodology, software engineering and hardware design. Niklaus Wirth passed away on the first of January. We mourn a pioneer, colleague, mentor and friend.
Whoa, LLM context lengths are getting long enough to store entire novels. That puts them within a few years of being able to read Boost's compile errors.
"Despite these challenges and limitations, we’ve still found Rust to be a significant improvement over C (or C++), both in terms of safety and productivity, in all the bare-metal use cases where we’ve tried it so far. We plan to use it wherever practical."
https://t.co/eSQMh6lWa1
@vzverovich Pretty zzz..
However, their latest community transparency report lists 6 incidents of someone on Discord referring to the Carbon community with a masculine pronoun, for which they were reprimanded.. so things seem preeeetty rowdy!
> be rust programmer
> ask the c++ programmer if their type is copy or move
> she laughs and says “it's a good type hikari”
> look up the header
> it's both
I mostly share your sentiment, but the sad truth is that Rust's metaprogramming is years behind C++'s.
Macros are not a substitute for type-level metaprogramming and compile-time evaluation.
#cpp#rust
Compiling to C is a common path for language backends. But compiling to C++ isn't, even though C++ has a big ecosystem and is hard to FFI against manually (only D and explicit C++ successors like Carbon/Circle even try?).
Serious q: why don't more languages use C++ as a backend?