crater
cppfront
crater | cppfront | |
---|---|---|
23 | 88 | |
619 | 5,132 | |
2.9% | - | |
7.8 | 9.5 | |
about 1 month ago | 3 days ago | |
Rust | C++ | |
- | 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.
crater
-
Semver violations are common, better tooling is the answer
yup, they reference it as an inspiration: https://github.com/rust-lang/crater
it's probably impossible to automate an entire ecosystem, and there is value to enabling a tighter integration within a project ecosystem (a subset of the language ecosystem).
-
Trip Summer ISO C++ standards meeting (Varna, Bulgaria)
Rather than hypothesising about an imagined tool you could look at the actual tool which of course is in Rust's source code repo: https://github.com/rust-lang/crater
> new proposed C++ changes - are checked against only easily and "well-known" accessible package.
Now that I have, so to say, shown you mine, lets see yours. Where is the tool to perform these checks in C++?
-
GCC 13 and the state of gccrs
The "break things" part of "move fast" is not essential, Rust cares so much about breakage they literally compile and run the tests for every crate on crates.io and github using a tool called Crater. They do this just to test changes, even for stuff thats documented to be unstable, because thats just courtesy. And tooling makes it trivial to switch between Rust versions.
-
Do one thing, and do it well, or not.
The bot's named Crater if you want to look into it more.
-
Improving Rust compile times to enable adoption of memory safety
See https://github.com/rust-lang/crater
-
Discussion about the state of neovim's plugin ecosystem
Rust compiler developers use a tool called Crater to test potentially breaking compiler changes on all crates (Rust's name for libraries) uploaded to the official repository. If plugin stability is the issue, maybe a solution along these lines would be better than merging these plugins to Neovim's core?
-
Experienced C++ users: what do you like about Rust? How would you sell it to other C++ users?
https://github.com/rust-lang/crater is the bot they use to test proposed compiler/stdlib changes against slices of the crates.io library up to and including "all of it".
-
Data-driven performance optimization with Rust and Miri
The tool you're referring to is called Crater: https://github.com/rust-lang/crater.
- GHC 9.4.2 regresses being able to do math on aarch64
-
Rust for Linux officially merged
I'm pretty certain this isn't actually true. You should look at the editions, etc. Rust also has an insane guarantee which I am certain C/C++ don't offer: It rebuilds its entire library ecosystem each time it ships to make sure nothing breaks (https://crater.rust-lang.org). I've never seen an instance were old code didn't compile on a new compiler. Rust isn't forwards compatible (new code compiles on an old compiler) of course, but what is?
cppfront
-
GCC 14.1 Release
CPP2/cppfront:
https://github.com/hsutter/cppfront
I hope we see this in C++26 as optional mode i.e. #safe and #unsafe and same for #impdef or so.
-
Compilation of gripping C++ conference talks from 2023
C++23 is done. But C++ is not! In this talk, the author shares his personal perspectives on an ongoing and very active evolution of C++, updates on his cppfront experimental compiler, and why compatibility is essential to the further success of the C++ development.
- Show HN: a Rust Based CLI tool 'imgcatr' for displaying images
- Cpp2 and cppfront – An experimental 'C++ syntax 2' and its first compiler
-
C++ Safety, in Context
https://github.com/hsutter/cppfront
But his side project at Microsoft didn't gain traction with gcc, clang, etc and everybody else in the industry. So at this point, the C++ committee will be perceived as "so far behind" ... because there's nothing for them to vote on.
- Cppfront: Experimental C++ Syntax 2 –> Syntax 1 compiler
- Odin Programming Language
- Cppfront
-
C++ Should Be C++
C++ has major flaws that cannot be rectified without serious breaking changes. With that said, Herb has been experimenting with a new cpp frontend with sane defaults [1].
In my opinion, the world is on standby until Anders Hejlsberg feels like tackling a modern, next generation systems language.
[1] https://github.com/hsutter/cppfront
- Why is the committee so reluctant to add new features to the language itself instead of stuffing them into the STL?
What are some alternatives?
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
actix-net - A collection of lower-level libraries for composable network services.
jakt - The Jakt Programming Language
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
serenity - The Serenity Operating System 🐞
AutoMapper - A convention-based object-object mapper in .NET.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
rust-prehistory - historical archive of rust pre-publication development
exotracker-cpp
NUnit - NUnit Framework
LoopModels - "Full speed or nothing." - James Hetfield