cargo-msrv
competitive-programming-rs
cargo-msrv | competitive-programming-rs | |
---|---|---|
11 | 2 | |
752 | 254 | |
- | - | |
9.1 | 2.0 | |
3 days ago | 9 months ago | |
Rust | Rust | |
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
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.
cargo-msrv
-
Introducing cargo-ft: a cargo extension for specifying supported targets for a crate
What this tool say? https://github.com/foresterre/cargo-msrv
-
What’s everyone working on this week (19/2023)?
I'm working on cargo-marv.
-
What's your crate's Minimum Supported Rust Version?
Before getting overcome by despair, have a look at cargo-msrv -- this little gem of a tool figures it all out for you!
-
What's everyone working on this week (31/2022)?
I'll be adding a 'minimal' output format to cargo-msrv for use in scripts. I'll also be updating the book, and inch closer towards releasing v0.16.
-
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.
-
[Gitoxide in January]: full multi-index support in object database and complete git-index reading
Looks helpful though it doesn't seem to address when you don't have a Cargo.lock. I've created an issue for this.
-
What’s everyone working on this week (8/2022)?
I'll be switching over the CLI of cargo-msrv, from Clap's builder methods to the attribute macro. I hope this will simplify the configuration, as my Config and ConfigBuilder structs (which were build from Clap's ArgMatches) was growing fast, and becoming slightly unorganized. With the attribute macro, the config will be constructed directly by code generated by the macro. The mostly saves one intermediate step, and a lot of boilerplate.
- cargo-msrv v0.14.0 release
-
Announcing `cargo supply-chain`: Know whom you trust
Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.
competitive-programming-rs
-
Why does std::io::Read::bytes() iterate over Result<u8, _> instead of just u8? And how to implement a scanner that returns Err immediately on an Err?
I have this question because, as practice, I'm trying to implement a struct Scanner based on this repo, and as an extra, I'd like to be able to handle errors instead of just panicking. However, unlike map(), the skip_while() and take_while() won't handle errors. If the Errs wouldn't happen unless in situations when the program were going very wrong, then I could just panic. Alternatively, is there a way to break and just return an error once bytes() gives an Err, with just iterator function chaining and without having to write loops myself?
-
What’s everyone working on this week (8/2022)?
This week I read about FnMut and FnOnce. I also found some amazing Rust code for parsing input/output for competitive programming , and solved all the google kickstart problems using it. I made two one hour video of my efforts starting here: https://youtu.be/EvL5YfPw8Ts
What are some alternatives?
toml-bombadil - A dotfile manager with templating
screwsat - A simple CDCL(Conflict-Driven-Clause-Learning) SAT solver in Rust.
crates.io-index - Registry index for crates.io
pdc
cargo-crev - A cryptographically verifiable code review system for the cargo (Rust) package manager.
bounded-static - A Rust crate that defines the ToBoundedStatic and IntoBoundedStatic traits
rust_lisp - A Rust-embeddable Lisp, with support for interop with native Rust functions
MakeGestureDataset - A Rust GUI application to quickly put together a dataset of gestures.
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).
Vital-Utilities - Vital Utilities. Modern Windows Task Manager alternative with bells and whistles
sniper - a cross-editor snippet manager featuring modular snippet sets