You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to confirm, is this an issue only with that rustc nightly feature flag active, which rust-gpu doesn't use? Isn't this then a regression in upstream rustc that activating that feature breaks existing rust code (which isn't surprising for a feature gate)?
Reading this I feel like you have enabled that nightly feature for your project, and it "works" on newer nightlies, but rust-gpu being and older nightly that feature breaks? And if we were to update to a newer nightly, we'd unblock you from using the feature in your code?
And while technically available as a feature in the version rust-gpu uses right now, it is even more hopelessly broken there, so it isn't really usable for me in that state.
I use generic_const_exprs heavily and the last nightly (ever, it is on the way out) where it is not broken is nightly-2026-05-03.
generic_const_args, which essentially is a successor, is still too broken even in the latest nightly (ICE in rustdoc and other issues) to be usable for everything unconditionally.
I'm not sure if it sufficiently not broken for non-rustdoc use cases in nightly-2026-05-22, I have seen some important fixes during last few weeks, so it is likely that I'll actually need nightly from June before I'll be able to upgrade rust-gpu.
Activity
Firestar99 commentedon Jun 6, 2026
Just to confirm, is this an issue only with that rustc nightly feature flag active, which rust-gpu doesn't use? Isn't this then a regression in upstream rustc that activating that feature breaks existing rust code (which isn't surprising for a feature gate)?
Reading this I feel like you have enabled that nightly feature for your project, and it "works" on newer nightlies, but rust-gpu being and older nightly that feature breaks? And if we were to update to a newer nightly, we'd unblock you from using the feature in your code?
nazar-pc commentedon Jun 6, 2026
This is actually expected (for now), that it breaks existing code, see rust-lang/rust#157152 and #project-const-generics > Need help migrating from GCE to GCA @ 💬.
And while technically available as a feature in the version rust-gpu uses right now, it is even more hopelessly broken there, so it isn't really usable for me in that state.
Firestar99 commentedon Jun 8, 2026
Is #610 sufficiently up-to-date for you? I've just forward ported to a nightly around where rustc 1.97 branched.
nazar-pc commentedon Jun 8, 2026
Possibly, but it is actually very complicated.
I use
generic_const_exprsheavily and the last nightly (ever, it is on the way out) where it is not broken isnightly-2026-05-03.generic_const_args, which essentially is a successor, is still too broken even in the latest nightly (ICE inrustdocand other issues) to be usable for everything unconditionally.I'm not sure if it sufficiently not broken for non-
rustdocuse cases innightly-2026-05-22, I have seen some important fixes during last few weeks, so it is likely that I'll actually need nightly from June before I'll be able to upgraderust-gpu.Firestar99 commentedon Jun 9, 2026
Is today's nightly sufficiently up-to-date? :D #612
nazar-pc commentedon Jun 9, 2026
Yes, it should be. Thanks!
nazar-pc commentedon Jun 11, 2026
#610 was indeed sufficiently recent for my needs so far