meta-rust
OpenEmbedded/Yocto layer for Rust and Cargo (by meta-rust)
libs-team
The home of the library team (by rust-lang)
Our great sponsors
| meta-rust | libs-team | |
|---|---|---|
| 2 | 13 | |
| 195 | 106 | |
| 1.0% | 3.8% | |
| 7.4 | 6.3 | |
| 3 months ago | 2 months ago | |
| NASL | Rust | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
meta-rust
Posts with mentions or reviews of meta-rust.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-13.
-
Advice: i.MX8X in Rust?
No patching Rust, what I did end up patching (for the reasons in my previous comment), was the Yocto Rust support layer, meta-rust - Rust support is present in mainline, but it's relatively slow with updates, and we're, for now, based on Kirkstone
-
Is anyone actually stuck on an old version of Rust
We depend on https://github.com/meta-rust/meta-rust which doesn't get updated regularly.
libs-team
Posts with mentions or reviews of libs-team.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-12.
-
Error when using cxx to link a Rust-written library in a C++ project
In rust, both release and debug builds use a release version of the runtime. The bugs the debug version is meant to catch are much more difficult to hit in rust (often but not always requiring unsafe). There isn't currently a feature to use the debug runtime in rust-- you can only change C to match for those debug builds.
-
log is going to bump msrv to 1.60
Note that this has been discussed at length (and I do mean "at length") here: https://github.com/rust-lang/libs-team/issues/72
-
Why We Love Rust: Ferris Is Only Part Of It
The Compiler Team, especially the Diagnostics Working Group that improves compiler error messages. The Libs Team, for work on the contents of the standard library documentation
-
Rust in 2023: Growing Up
See https://github.com/rust-lang/libs-team/issues/72#issuecommen... for what I believe is an exhaustive list of possible ways of helping the situation.
-
time: MSRV policy is changing beginning 2023-07-01 to N-2 rustc versions
The point is how the MSRV of a popular crate affects this dynamic for other crates. For an even more extreme example than time, see here for libc, with many heavyweights offering opinions: https://github.com/rust-lang/libs-team/issues/72
-
What are binary crate MSRV policy best practices?
In case you haven't seen it yet, there is a very long discussion surrounding MSRV policy of the libc crate on rust-langs github repo. It's about a library, not a binary, but I think there's a lot of information in the thread, some of which will also apply to binaries.
-
(pre-announcing) clap 4.0, a Rust CLI argument parser
Would you mind sharing your use case for being stuck with a particular version of Rust and why you can't upgrade? In particular with the libs team: https://github.com/rust-lang/libs-team/issues/72
-
Azure CTO: “It's time to halt starting any new projects in C/C++ ”
Compare Stepanov's brilliant design of the STL to Rust's current reworking of their 'binary search api'. https://github.com/rust-lang/libs-team/issues/81
Maybe 'memory safety' isn't the most important thing in this world. To me, writing software that does useful things in the simplest and most correct way is what matters. I get the feeling it's harder to understand my program's correctness with Rust (I mean algorithmic correctness). The C++ standard library has time and space complexity for every algorithm. I'm not seeing that's the case with Rust (correct me if I'm wrong).
-
Is anyone actually stuck on an old version of Rust
There's also the pretty fundamental libc crate that wants to choose an MSRV policy and you can see the full discussion here: https://github.com/rust-lang/libs-team/issues/72
- For rust, I have never see a real world project contains million lines of code, nor more than 1000 components here.
What are some alternatives?
When comparing meta-rust and libs-team you can also consider the following projects:
poky - Mirror of https://git.yoctoproject.org/poky/.
awesome-rust - A curated list of Rust code and resources.