surveys
cargo-patch
| surveys | cargo-patch | |
|---|---|---|
| 3 | 1 | |
| 28 | 60 | |
| - | - | |
| 8.3 | 2.8 | |
| 3 months ago | 13 days ago | |
| Python | Rust | |
| - | MIT License |
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.
surveys
-
The Rust Trademark Borrow Checker : Rust Foundation Solicits Feedback on Updated Policy for Trademarks
The latest Rust survey with results published is the 2021 survey with out of the 49% of those surveyed that had participated in official chats or forums only 2% said they never felt welcomed and only 9% said they only sometimes feel welcomed (source on page 29). That's ~4/5 people that did participate in official communication that definitely felt welcomed and ~49/50 that didn't feel unwelcomed, which is much more inline with my experience in the Rust community for the past 5 years.
- Announcing Rustup 1.25.1
-
Rust for the Kernel Could Possibly Be Merged for Linux 5.20
Less than 20% of devs use nightly. About a third of the devs who use nightly do it because of a dependency. A far cry from the “half” claimed by GP.
https://github.com/rust-lang/surveys/raw/main/surveys/2021-a...
cargo-patch
-
Rust for the Kernel Could Possibly Be Merged for Linux 5.20
First commit 2 months ago, started with edition 2021. https://hg.sr.ht/~cyplo/legdur/browse/Cargo.toml?rev=ca11815...
Have you tried compiling something less than bleeding edge, with a year old compiler, or are you picking projects specifically to "showcase" the supposed failings of the Rust compiler?
Many libraries in the ecosystem have a MSRV (minimum support rust version) guarantee, with compile-time shims to enable newer features if a more recent version is detected.
You can pin your dependencies to those versions (and if they don't have an explicit MSRV, just pin it to a version by date or by running https://github.com/foresterre/cargo-msrv on the project to find the effective MSRV).
You can cargo install specific versions of a binary crate, and if they move to the 2021 edition, or use a recently stabilized standard library function or w/e, you can simply choose to install a specific version, that would work with your distro's rustc/cargo.
I'm not even talking about the completely valid, but last resort strategy of many non-bleeding edge distro package maintainers, of simply creating a .patch file and applying it. In legdur's case, --- edition = "2021" +++ edition = "2018" on Cargo.toml would probably do the trick. For libraries/binaries you control, you can use https://doc.rust-lang.org/cargo/reference/overriding-depende... and https://github.com/itmettkeDE/cargo-patch.
Giving up after the first minor roadblock and crying bloody murder is intellectually lazy.
What are some alternatives?
cargo-deb - A cargo subcommand that generates Debian packages from information in Cargo.toml
gccrs - GCC Front-End for Rust
jakt - The Jakt Programming Language
netbsd-sandbox - The secmodel_sandbox security module for NetBSD
crab - A community fork of a language named after a plant fungus. All of the memory-safe features you love, now with 100% less bureaucracy!
rust - Empowering everyone to build reliable and efficient software.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
rust-artwork - Official artwork for the Rust project.
cargo-msrv - 🦀 Find the minimum supported Rust version (MSRV) for your project