Maybe it's a good time to consider migrating from a fixed MSRV policy to a flexible one (last N versions), to avoid MSRV bump requires a major bump. #725
Description
I totally agree, but I think it should be a maintainers' decision.
In my opinion, I don't get why people expect to be able to use an ancient compiler with new libraries. If somebody uses such an old rustc version, they should expect that something will break from time to time.
And for me it shouldn't be considered as a breaking change because sometimes there may be that kind of a situation:
- We found a security bug, which we can reproduce only on a specific version of the compiler
- We want all our users, who didn't fix a patch version, to update
- We update an msvr in a patch version due to the bug
It doesn't affect the code itself, only the environment. Of course, it can be a bit of a pain when people have a well-established CI pipeline pinned to a specific Rust version, but in such a case, I think it’s a fair price to pay.
N - 2 may be a good policy due to https://lib.rs/stats#rustc: 0% of crates are considered as "not compatible" in that version
If the decision is made, I’ll prepare a PR.