Skip to content

Update Rust toolchain #605

Closed

Description

@nazar-pc

Generics in latests nightlies with generic_const_args require const {} rather than {} in places like this:

atomic_i_increment::<_, { Scope::QueueFamily as u32 }, { Semantics::NONE.bits() }>(..)

This makes writing code that compiles both with rust-gpu's old toolchain version and latest nightly very frustrating.

Please consider updating toolchain again some time soon 🙏

Activity

  1. Firestar99 commented on Jun 6, 2026

    @Firestar99
    Member

    with generic_const_args

    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?

  2. nazar-pc commented on Jun 6, 2026

    @nazar-pc
    ContributorAuthor

    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.

  3. Firestar99 commented on Jun 8, 2026

    @Firestar99
    Member

    Is #610 sufficiently up-to-date for you? I've just forward ported to a nightly around where rustc 1.97 branched.

  4. nazar-pc commented on Jun 8, 2026

    @nazar-pc
    ContributorAuthor

    Possibly, but it is actually very complicated.

    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.

  5. Firestar99 commented on Jun 9, 2026

    @Firestar99
    Member

    Is today's nightly sufficiently up-to-date? :D #612

  6. nazar-pc commented on Jun 9, 2026

    @nazar-pc
    ContributorAuthor

    Yes, it should be. Thanks!

  7. nazar-pc commented on Jun 11, 2026

    @nazar-pc
    ContributorAuthor

    #610 was indeed sufficiently recent for my needs so far

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions