Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.37.0 introduced code that isn't stable with 1.64 #750

Closed
1 task done
CraZySacX opened this issue Feb 20, 2023 · 1 comment
Closed
1 task done

0.37.0 introduced code that isn't stable with 1.64 #750

CraZySacX opened this issue Feb 20, 2023 · 1 comment
Assignees

Comments

@CraZySacX
Copy link

Duplicates

  • I have searched the existing issues

Current behavior 😯

When compiling with 1.64 I get the following error:

error[E0658]: let...else statements are unstable
--> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/gix-0.37.0/src/object/tree/diff/for_each.rs:135:9
|
135 | / let Some(tracked) = self.tracked.as_mut() else {
136 | | return Ok(None)
137 | | };
| |__________^
|
= note: see issue #87335 rust-lang/rust#87335 for more information

I dug a bit into the RFC and it appears this became stable in 1.65. You may just want to bump the MSRV to 1.65.

Expected behavior 🤔

Well, if you wish to keep 1.64 as the MSRV this would need to compile against it.

Steps to reproduce 🕹

No response

@Byron Byron self-assigned this Feb 21, 2023
Byron added a commit that referenced this issue Feb 21, 2023
Also, this makes it easier to let people build with their preferred version, now that the msrv
is registered in each crate rustc will refuse to build crates that are not compatible, I think.

Otherwise it will download a different version of the compiler right before building it
Byron added a commit that referenced this issue Feb 21, 2023
Also, this makes it easier to let people build with their preferred version, now that the msrv
is registered in each crate rustc will refuse to build crates that are not compatible, I think.

Otherwise it will download a different version of the compiler right before building it
@Byron
Copy link
Owner

Byron commented Feb 21, 2023

Thanks for reporting!

After investigating this it turned out that CI didn't catch it because:

  • the rust-toolchain.toml file caused an auto-download of the rustc version configured there, which was 1.65. The pipeline didn't actually test what I thought it would.
  • the job was configured to continue on error due to some other issue in the dependency tree which by now was fixed.

This is why the problem shouldn't occour again.

I also published a new patch release with the fix: 0.37.1.

Closing as the issue is provably fixed. Please let me know if there is anything else.

@Byron Byron closed this as completed Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants