Matthias Krüger f4335a419f Rollup merge of #119540 - fmease:no-effect-args-inside-dyn-trait, r=compiler-errors ... Don't synthesize host effect args inside trait object types While we were indeed emitting an error for `~const` & `const` trait bounds in trait object types, we were still synthesizing host effect args for them. Since we don't record the original trait bound modifiers for dyn-Trait in `hir::TyKind::TraitObject` (unlike we do for let's say impl-Trait, `hir::TyKind::OpaqueTy`), AstConv just assumes `ty::BoundConstness::NotConst` in `conv_object_ty_poly_trait_ref` which given `<host> dyn ~const NonConstTrait` resulted in us not realizing that `~const` was used on a non-const trait which lead to a failed assertion in the end. Instead of updating `hir::TyKind::TraitObject` to track this kind of information, just strip the user-provided constness (similar to #119505). Fixes #119524.		2024-01-04 08:33:26 +01:00
..
src	Rollup merge of #119540 - fmease:no-effect-args-inside-dyn-trait, r=compiler-errors	2024-01-04 08:33:26 +01:00
Cargo.toml	Clean up rustc_*/Cargo.toml.	2023-10-30 08:46:02 +11:00
messages.ftl	Deny defaults for higher-ranked generic parameters	2024-01-01 21:58:25 +01:00