Skip to content

Tracking Issue for for-loops in constants #87575

Open

Description

@jonas-schievink

This tracks #![feature(const_for)], added in #87237.

This feature depends on const_trait_impl and is not currently usable.

Activity

  1. SUPERCILEX commented on Mar 25, 2022

    @SUPERCILEX
    Contributor

    Is there a tracking issue for const range iterators? Doing something like for i in 0..1000 { doesn't compile... am I missing something?

  2. CalinZBaenen commented on Jun 18, 2022

    @CalinZBaenen
  3. mati865 commented on Jun 20, 2022

    @mati865
  4. CalinZBaenen commented on Jun 21, 2022

    @CalinZBaenen
  5. mati865 commented on Jun 21, 2022

    @mati865
  6. CalinZBaenen commented on Jun 21, 2022

    @CalinZBaenen
  7. Tom1380 commented on Sep 22, 2023

    @Tom1380
  8. Crypto-Spartan commented on Aug 15, 2024

    @Crypto-Spartan

    Any updates on this?

  9. oli-obk commented on Aug 15, 2024

    @oli-obk
    Contributor

    const_traits is still very unstable. @fee1-dead is doing the refactoring on this and has recently landed a major milestone. There are still many things to resolve though.

    Consider sponsoring (https://github.com/sponsors/fee1-dead) as a thank you if this work is important to you

  10. added
    A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)
    and removed on Dec 1, 2024
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

    A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions