Tracking Issue for `feature(min_adt_const_params)`

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

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

• Implement the RFC (cc @rust-lang/XXX -- can anyone write up mentoring
  instructions?)
• Adjust documentation (see instructions on rustc-dev-guide)
• Style updates for any new syntax (nightly-style-procedure)
  • Style team decision on new formatting
  • Formatting for new syntax has been added to the Style Guide
  • (non-blocking) Formatting has been implemented in rustfmt
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

Should the field privacy restriction be based on equivalent privacy levels, or on fields being at least as public as the ADT

Implementation history

• #153592

Start with the feature gate #![feature(min_adt_const_params)] and the implementation history entry for PR #153592. Review the unresolved question about field privacy, then consult the linked rustc-dev-guide stabilization and documentation instructions. Done means the RFC implementation, documentation, and stabilization checklist items are completed.