rust_lisp VS cargo-msrv

Well, the article is called "a simple Lisp", not "a fully featured Lisp". It's a demo, not a compliant implementation.

You may be interested by https://github.com/brundonsmith/rust_lisp though

So to compensate, strop will now be usable as a library. So I'm making a thing which pulls in strop as a dependency and gives you a dialect of lisp for you to specify your function in. In the future, perhaps I'll do the same with Python and maybe others. In this way, the end users will have a better way to specify what they want.

Plug: for fun I made a (less ambitious) version of this kind of thing for Rust which I ended up being pretty happy with

https://github.com/brundonsmith/rust_lisp

What this tool say? https://github.com/foresterre/cargo-msrv

I'm working on cargo-marv.

Before getting overcome by despair, have a look at cargo-msrv -- this little gem of a tool figures it all out for you!

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.

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.

Looks helpful though it doesn't seem to address when you don't have a Cargo.lock. I've created an issue for this.

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.

Some combination of cargo-outdated and cargo-msrv could probably do this in a slightly more manual fashion.