undefined | Better HN

0 pointsdjsumdog6y ago0 comments

This is one of the biggest problems I've had with any neat Rust thing posted up here. The language changes a lot. I have rust/cargo 1.37.0 installed (it's the latest marked stable in Gentoo) and adler32 v1.0.4 fails to compile with "`core::slice::<impl [T]>::len` is not yet stable as a const fn". I'm installing 1.40.0 from the unstable tree to see if that will build it.

I've had situations where I'm either not on the latest version of rust, or I'm on too current a version of rust, which deprecated/removed some feature needed for a dependency. I'm not sure if devs can define their min/max versions, but that kinda check should probably be done before cargo starts building packages.

0 comments

StavrosK6y ago

Agreed, and I had the same problem. It seems like an easy fix to add a requires_rust_version thing in Cargo.toml, and devs could at least set it to "the version I'm currently using" so we know it's guaranteed to build on that.

steveklabnik6y ago

It’s not that easy; the real world has a lot of complexity. That said, we finally did accept a design for this in October; it’s not clear when it’s going to land though.

StavrosK6y ago

Because of dependencies, you mean? Even an indication of "this builds fine for me at version X" would be good.

1 more reply

mlindner6y ago

There's no such thing as a "too current a version of rust". All Rust compilers (since 1.0) compile all previous versions of code and will continue to do so.

In the rare case you might hit something that was removed/modified because of a security exploit, but those are very very rare.

edflsafoiewq6y ago

This is not true in practice. Old code has failed to compile for various reasons; off the top of my head, new additions to the prelude, and denied lints that became more restrictive. It's not super rare.

zlynx6y ago

Just a nitpick: Rust 1.40 seems to be the stable version for a couple of weeks now.

j / k navigate · click thread line to collapse

0 pointsdjsumdog6y ago0 comments

0 comments

StavrosK6y ago

steveklabnik6y ago

It’s not that easy; the real world has a lot of complexity. That said, we finally did accept a design for this in October; it’s not clear when it’s going to land though.

StavrosK6y ago

Because of dependencies, you mean? Even an indication of "this builds fine for me at version X" would be good.

1 more reply

mlindner6y ago

There's no such thing as a "too current a version of rust". All Rust compilers (since 1.0) compile all previous versions of code and will continue to do so.

In the rare case you might hit something that was removed/modified because of a security exploit, but those are very very rare.

edflsafoiewq6y ago

zlynx6y ago

Just a nitpick: Rust 1.40 seems to be the stable version for a couple of weeks now.

j / k navigate · click thread line to collapse