Tracking Issue for Generic Constant Arguments MVP

This is a tracking issue for the prototype described in rust-lang/rust-project-goals#100. Background reading as to the design/justification for this feature.
The feature gate for the issue is #![feature(min_generic_const_args)].

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Add ConstArgKind::Path (Represent type-level consts with new-and-improved hir::ConstArg #125915)
• Use ConstArgKind::Path for all single-segment paths (Use ConstArgKind::Path for all single-segment paths, not just params under min_generic_const_args #131081)
• Use ConstArgKind::Path for all paths
  • most paths mgca: Lower all const paths as ConstArgKind::Path #135186
  • Support ConstArgKind::Path for uses of static paths #132986
• Support "simple" exprs necessary for constructing adt_const_params types:
  • Struct construction exprs, e.g. Adt { field: N }
    • Core impl MGCA: Support struct expressions without intermediary anon consts #149114
    • Rest patterns MGCA: support struct expressions with ..rest patterns as direct const args? #150622
  • Tuple constructor calls, e.g. Some(N) MGCA: support tuple constructor calls as a direct const argument #150610
  • Const constructs, e.g. None Support ConstArgKind::Paths for const struct/variant constructors #132985
  • Array exprs, e.g. [M; N], [1, 2, N] MGCA: Support array expressions as direct const arguments #150612
  • Tuple exprs, (10, N) MGCA: Support tuple expressions as direct const arguments #150613
• reject impls not using #[type_const] on their assoc consts if the trait used it mgca: Finish implementation of #[type_const] #148716
• enforce type_const marked const items have a type that implements ConstParamTy mgca: Finish implementation of #[type_const] #148716
• forbid generic parameters from being used in the types of const parameters MGCA: forbid generic parameters from being in used in the types of type_const items #150614
• lower uses of type_consts to mir::Const::Ty so they can be normalized in the MIR correctly MGCA: uses of type_const items inside of bodies should lower to mir::Const::Ty #150615
• Make inherent associated constants behave correctly rustc internal compiler error: 'rustc' failed at 'Box<Any>' #15200
• Implement type system normalization that makes use of associated_const_equality bounds mgca: Add ConstArg representation for const items #139558
• Merge feature(associated_const_equality) into min_generic_const_args MGCA: merge associated_const_equality feature gate into MGCA #150617
• Experiment with adding some kind of ConstArgKind::Literal MGCA: Support literals as direct const arguments #150618
• Traits are dyn compatible if all associated consts are type safe Permit trait object types where all (non-generic) associated constants are specified (via assoc item bindings) #130300
• Find a way to avoid code duplication between HIR ty lowering and typechecking for struct expressions MGCA: Avoid code duplication between HIR ty lowering and elsewhere #150621
• Make HIR ty lowering lower uses of generic parameters to errors if in an item with no generics
  • ish, Use more principled check for generics in const ops #150519
  • Validate HIR ty lowering's produced generic parameters #150620
• Find better names for ConstKind::Value and ValTree now that they're not fully evaluated Followup work from making ValTree recurse through ty::Const #150624
• Do something about CTFE returning ValTrees with erased lifetimes. Likely means adding a ValTree which doesn't recurse through ty::Const like how it used to be Followup work from making ValTree recurse through ty::Const #150624
• Typecheck that const arguments outside of paths have the correct type MGCA: Check that const arguments in struct exprs are correctly typed #150623
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• Can we get rid of needing an annotation on const items for them being type consts?
  • If no we need t-style to decide on rustfmt stuff

Implementation history