-
Notifications
You must be signed in to change notification settings - Fork 132
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
Conversation
Prepublished as |
There was a problem hiding this 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?
Yeah, me too! I hope that this means less nightly breakage in the future.
Not sure what the advantage of that would be. The CI already uses the latest nightly and it wouldn't help people that use |
That makes sense. SGTM for leaving it as is. |
Looks like the |
Thanks, I will update to the pre-release version of the crate now probably. |
Yes, thanks for the ping! |
Published as |
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