Tracking issue for rust-lang/rfcs#2000

Updates:

• 2 May 2019: Tracking issue for const generics (RFC 2000) #44580 (comment)
• 19 Oct 2019: Tracking issue for const generics (RFC 2000) #44580 (comment)
• 2 Jan 2020: Tracking issue for const generics (RFC 2000) #44580 (comment)
• 22 Jul 2020: Tracking issue for const generics (RFC 2000) #44580 (comment)
• 17 Nov 2020: Tracking issue for const generics (RFC 2000) #44580 (comment)
• 11 Dez 2021: Tracking issue for const generics (RFC 2000) #44580 (comment)

If you want to help out, take a look at the open const generics issues and feel free to ping @varkor, @eddyb, @yodaldevoid, @oli-obk or @lcnr for help in getting started!

Blocking stabilization:

• Design:
  • Resolving ordering of const and type parameters, with default parameters
  • Decide what the best UX / implementation cost balance is for unifying abstract const expressions.
  • How we determine well formedness of const expressions.
• Implementation
• Documentation
  • rustc guide

Remaining implementation issues:

• Resolve various FIXME(const_generics) comments.
• Resolve concerns with canonicalisation / lazy normalisation.
• Investigate handling of const parameters in patterns.
• Add more tests.
• Implement defaults for const parameters (FIXME(const_generics_defaults)).
• Fix other A-const-generics issues.
• Audit uses of has_infer_types.
• Forbid complex expressions for const arguments involving parameters (for now), e.g. {X * 2}.
• Audit diagnostics (e.g. Add help note to unconstrained const parameter #76401 (comment)).