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

Use new const_fn_trait_bound feature to fix build on latest nightly #250

Merged
merged 1 commit into from
May 6, 2021

Conversation

phil-opp
Copy link
Member

@phil-opp phil-opp commented Apr 30, 2021

Feature gate introduced in rust-lang/rust#84310.

Unfortunately, unknown feature gates lead to errors so that this change errors on older nightlies. For this reason, I think we should at least wait until the common rustfmt component is fixed on nightly again because then everyone should be able to update. See https://rust-lang.github.io/rustup-components-history/ for component availability.

Fixes #252

@phil-opp
Copy link
Member Author

Prepublished as v0.14.1-beta in case someone is already using the latest nightly.

Copy link
Contributor

@josephlr josephlr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great!! I'm glad the catch-all const_fn feature is finally going away.

Given that this change will break all users on previous nighties, should we update the rust-toolchain file to point to a specific nightly?

@phil-opp
Copy link
Member Author

phil-opp commented May 1, 2021

Yeah, me too! I hope that this means less nightly breakage in the future.

Given that this change will break all users on previous nighties, should we update the rust-toolchain file to point to a specific nightly?

Not sure what the advantage of that would be. The CI already uses the latest nightly and it wouldn't help people that use x86_64 as a dependency. It would help people on older nightlies that try to contribute to this crate, but the disadvantage is that our CI would no longer test with the latest nightly then.

@josephlr
Copy link
Contributor

josephlr commented May 6, 2021

Given that this change will break all users on previous nighties, should we update the rust-toolchain file to point to a specific nightly?

Not sure what the advantage of that would be. The CI already uses the latest nightly and it wouldn't help people that use x86_64 as a dependency. It would help people on older nightlies that try to contribute to this crate, but the disadvantage is that our CI would no longer test with the latest nightly then.

That makes sense. SGTM for leaving it as is.

@josephlr
Copy link
Contributor

josephlr commented May 6, 2021

Looks like the 2021-05-06 nightly has fixed components. @phil-opp should we merge this?

@HTGAzureX1212
Copy link

republished as v0.14.1-beta in case someone is already using the latest nightly.

Thanks, I will update to the pre-release version of the crate now probably.

@phil-opp
Copy link
Member Author

phil-opp commented May 6, 2021

Looks like the 2021-05-06 nightly has fixed components. @phil-opp should we merge this?

Yes, thanks for the ping!

@phil-opp phil-opp merged commit c9e1960 into master May 6, 2021
@phil-opp phil-opp deleted the const_fn_trait_bound branch May 6, 2021 11:57
phil-opp added a commit that referenced this pull request May 6, 2021
@phil-opp
Copy link
Member Author

phil-opp commented May 6, 2021

Published as v0.14.1.

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

Successfully merging this pull request may close these issues.

Crate Does Not Compile on Rust 1.54 Nightly
3 participants