rust-lang/project-const-traits

Issues

• Add const stability tracking for traits

  #16 opened 9 months ago
  1

• Constifying large traits in libstd (i.e. `Iterator`)

  #15 opened a year ago
  3

• erasable `const`-ness on types and `TypeId`

  #14 opened a year ago
  2

• `PartialEq` and matching in const contexts

  #13 opened a year ago
  1

• Soundness hole: We don't catch non-const assoc fns in const contexts if the trait isn't `#[const_trait]`

  #12 opened a year ago
  3

• Conditionally const bounds (`~const`) in inherent impl headers

  #11 opened a year ago
  1

• Const closures

  #10 opened a year ago
  0

• Const opaques

  #9 opened a year ago
  0

• Diagnostic improvements

  #8 opened a year ago
  0

• Making impls const across bootstrap versions

  #7 opened a year ago
  2

• We should be enforcing constness predicates on all call-like things in HIR typeck

  #6 opened a year ago
  2

• Const stability on impls doesn't make sense

  #5 opened 8 months ago
  8

• Where does the `bool` go? (or: positioning of the effect param on traits)

  #4 opened a year ago
  1

• Don't force the user to specify effects for projections

  #3 opened a year ago
  2

• Making it possible to call super trait methods with bound on the subtrait

  #2 opened a year ago
  2

• Making

  #1 opened a year ago
  1