-
Notifications
You must be signed in to change notification settings - Fork 288
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
mark const fn constructors as rustc_const_stable_indirect #586
mark const fn constructors as rustc_const_stable_indirect #586
Conversation
I assume you need a new hashbrown release with this? |
Yeah to use this in std this will need a release.
|
I think you won't be able to bootstrap that until the new attribute reaches beta for stage0. |
Ah, true, good point. There's a beta branching in about a week so that's not too long of a wait. :) But I should probably double-check that this will actually work... |
…r=compiler-errors check_consts: fix error requesting feature gate when that gate is not actually needed When working on rust-lang/hashbrown#586 I noticed that the compiler asks for the `rustc_private` feature to be enabled if one forgets to set `rustc_const_stable_indirect` on a function -- but enabling `rustc_private` would not actually help. This fixes the diagnostics. r? `@compiler-errors`
I checked that if I do make these |
The bootstrap bump should happen any day now. @Amanieu would be nice to get a release. :) |
Done |
This is a promise that they can be implemented entirely using stable const features (and the compiler checks this when
-Zforce-unstable-if-unmarked
is set).Part of rust-lang/rust#102575.