about summary refs log tree commit diff
path: root/compiler/rustc_hir_analysis/messages.ftl
diff options
context:
space:
mode:
authorLeón Orell Valerian Liehr <me@fmease.dev>2025-06-19 18:41:57 +0200
committerLeón Orell Valerian Liehr <me@fmease.dev>2025-07-18 12:13:30 +0200
commit879f62bb3c23b7a90ac71bb217056fd49ff8dafb (patch)
tree904d0ae05b624b8b5b655628324394f0d8402b0e /compiler/rustc_hir_analysis/messages.ftl
parent84ed70b69daa6865d3713d36fabad90a2fb96afd (diff)
downloadrust-879f62bb3c23b7a90ac71bb217056fd49ff8dafb.tar.gz
rust-879f62bb3c23b7a90ac71bb217056fd49ff8dafb.zip
Reword diagnostic about relaxing non-`Sized` bound
* The phrasing "only does something for" made sense back when this
  diagnostic was a (hard) warning. Now however, it's simply a hard
  error and thus completely rules out "doing something".
* The primary message was way too long
* The new wording more closely mirrors the wording we use for applying
  other bound modifiers (like `const` and `async`) to incompatible
  traits.
* "all other traits are not bound by default" is no longer accurate
  under Sized Hierarchy. E.g., traits and assoc tys are (currently)
  bounded by `MetaSized` by default but can't be relaxed using
  `?MetaSized` (instead, you relax it by adding `PointeeSized`).
* I've decided against adding any diagnositic notes or suggestions
  for now like "trait `Trait` can't be relaxed as it's not bound by
  default" which would be incorrect for `MetaSized` and assoc tys
  as mentioned above) or "consider changing `?MetaSized` to
  `PointeeSized`" as the Sized Hierarchy impl is still WIP)
Diffstat (limited to 'compiler/rustc_hir_analysis/messages.ftl')
0 files changed, 0 insertions, 0 deletions