ipr
carbon-lang
ipr | carbon-lang | |
---|---|---|
4 | 174 | |
216 | 32,216 | |
- | 0.3% | |
5.0 | 9.8 | |
10 months ago | about 19 hours ago | |
C++ | C++ | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ipr
-
Module interfaces for pre-built libraries
I'm not sure about clang or gcc. For VS, u/GabrielDosReis might be able to speak to the .ifc IPR stability/volatility. My wager (deferring to him to correct me) is that the IPR is still changing over time but will stabilize more over time.
-
A new design pattern: the C++ "template mixin"
Have you had a look at its uses in the IPR interface and implementation? https://github.com/GabrielDosReis/ipr/blob/main/include/ipr/interface
-
Carbon Language: An experimental successor to C++
> C++ has virtually zero tooling
CMake, Meson, Waf, Conan, Visual Studio Code, Visual Studio, CLion, Intel VTune, GDB, LLDB, XCode, Artifactory, SonarQube, clang-tidy, clang-format, astyle, Incredibuild...
> Comparing CMake to cargo is like comparing fifth century fireworks to the Space Shuttle
You are wrong here. Cargo serves a set of fixed "this-is-how-to-do-it" thing. In C++ you can build anything. I do not mean it is better, but C++ software already exists and that is the solution that it works better for it. :)
> and the committee is not interested in ever working on that
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p08...
Interoperability effort for modules: https://github.com/GabrielDosReis/ipr
-
I hope this would ease C++ tooling
IPR Library
carbon-lang
- Carbon Copy Newsletter No.2
-
Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
The roadmap for Carbon [0] mentions wanting to have basic, non-trivial programs written in Carbon by the end of 2024. They're aiming for a v0.1 release in 2025. If it gains traction, they're aiming for a v1.0 beyond 2027.
I don't think anyone outside Google will seriously adopt this before it reaches v1.0. Even within Google, they may choose other options.
[0] - https://github.com/carbon-language/carbon-lang/blob/trunk/do...
- Carbon Language Newsletter, the Carbon Copy, February 2024
-
Odin Programming Language
Carbon was started by Chandler Carruth, at Google, but they wanted to move it to broader governance quickly. It's not under the Google GitHub today, but its own org.
https://github.com/carbon-language/carbon-lang/blob/trunk/do...
-
C++ Should Be C++
What do you think about Carbon[1]? I am hopeful.
[1] https://github.com/carbon-language/carbon-lang
- The NSA advises move to memory-safe languages
- Carbon Language: An experimental successor to C++
-
Toward a TypeScript for C++"
https://github.com/carbon-language/carbon-lang/blob/trunk/do...
next year 0.1 will be usable, 1.0 is about 3 years away, sigh, back to my rust fight
-
Programming Languages Every Developer Should Watch Out For
1. Carbon
What are some alternatives?
ifc-spec - IFC format specification
rust - Empowering everyone to build reliable and efficient software.
crubit
DIPs - D Improvement Proposals
cppfront - A personal experimental C++ Syntax 2 -> Syntax 1 compiler
verdigris - Qt without moc: set of macros to use Qt without needing moc
Odin - Odin Programming Language
PythonNet - Python for .NET is a package that gives Python programmers nearly seamless integration with the .NET Common Language Runtime (CLR) and provides a powerful application scripting tool for .NET developers.
go - The Go programming language
GrayC - GrayC: Greybox Fuzzing of Compilers and Analysers for C
hylo - The Hylo programming language