Hacker News Reader

That very very very much sounds like a bug, one that I’ve never heard of before. You don’t happen to have that project lying around, do you?

View on HN

It sounds little bit like the (known) situation around cargo where it doesn't default to `--locked` and so results in surprising behaviour for many people.

This particular issue is in regard to `cargo install`: https://github.com/rust-lang/cargo/issues/7169

Oh, or, I guess, it might be how the version is specified--guess we need some more details on what "compile something after it wasn’t touched for a year" entailed.

Oh, yes, with cargo install that is the case. They just said “cargo”. That would make more sense, yes.

I think I’ve noticed that cargo install would pick up newer semver-compatible versions than what was in the lockfile unless I passed —-locked explicitly, which seemed surprising to me.

Ah yeah if we’re talking about cargo install, then sure. That would make sense.

Both behaviors can be surprising. We picked one. It happens. I am not sure myself if it was the right choice or not.

Reply on news.ycombinator.com