Skip to content

Tracking Issue for transmute_generic_consts #109929

Open

Description

@JulianKnodt

The feature gate for the issue is #![feature(transmute_generic_consts)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

  • Maybe feature gate should be generic_const_array_size?

XXX --- list all the "unresolved questions" found in the RFC to ensure they are
not forgotten

Implementation history

Implemented in #106281

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Apr 4, 2023
  2. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Apr 5, 2023
  3. lcnr commented on Apr 18, 2023

    @lcnr
    Contributor

    this feels very related to the work of the safe transmute working group, cc #99571

  4. lcnr commented on Apr 18, 2023

    @lcnr
    Contributor

    I don't think we should add many hacks to the current transmute check and don't believe that an implementation which does so should be stabilized. I would instead expect to also handle this as part of the BikeshedIntrinsicFrom trait.

  5. dvdhrm commented on Jul 24, 2023

    @dvdhrm
    Contributor

    FYI: The feature gate is called transmute_generic_consts (rather than wrongly referenced in title and summary: transmute_const_generics).

  6. changed the title [-]Tracking Issue for `transmute_const_generics`[/-] [+]Tracking Issue for `transmute_generic_consts`[/+] on Jul 24, 2023
  7. added a commit that references this issue on Mar 7, 2024
  8. added a commit that references this issue on Mar 23, 2024
  9. added
    T-langRelevant to the language team
    and removed
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Nov 9, 2024
  10. zachs18 commented on Apr 17, 2026

    @zachs18
    Contributor

    I think the part of #106281 that actually constructed SizeSkeleton::Generic was effectively reverted by #122820, so I'm not sure that SizeSkeleton::Generic actually does anything currently? (i.e. it seems like it is never constructed)

    (This is unrelated to #114009 whose change is also gated under this feature)

  11. added
    T-typesRelevant to the types team, which will review and decide on the PR/issue.
    on Apr 17, 2026
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

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-langRelevant to the language teamT-typesRelevant to the types team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions