rust/tests/ui/consts/issue-94675.stderr

error[E0015]: cannot call non-const operator in constant functions
  --> $DIR/issue-94675.rs:11:17
   |
LL |         self.bar[0] = baz.len();
   |                 ^^^
   |
note: impl defined here, but it is not `const`
  --> $SRC_DIR/alloc/src/vec/mod.rs:LL:COL
   = note: calls in constant functions are limited to constant functions, tuple structs and tuple variants

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0015`.
fix library and rustdoc tests 2023-04-16 11:12:37 +00:00			`error[E0015]: cannot call non-const operator in constant functions`
Improve spans for indexing expressions Indexing is similar to method calls in having an arbitrary left-hand-side and then something on the right, which is the main part of the expression. Method calls already have a span for that right part, but indexing does not. This means that long method chains that use indexing have really bad spans, especially when the indexing panics and that span in coverted into a panic location. This does the same thing as method calls for the AST and HIR, storing an extra span which is then put into the `fn_span` field in THIR. 2023-08-03 19:43:17 +00:00			`--> $DIR/issue-94675.rs:11:17`
fix library and rustdoc tests 2023-04-16 11:12:37 +00:00			`\|`
			`LL \| self.bar[0] = baz.len();`
Improve spans for indexing expressions Indexing is similar to method calls in having an arbitrary left-hand-side and then something on the right, which is the main part of the expression. Method calls already have a span for that right part, but indexing does not. This means that long method chains that use indexing have really bad spans, especially when the indexing panics and that span in coverted into a panic location. This does the same thing as method calls for the AST and HIR, storing an extra span which is then put into the `fn_span` field in THIR. 2023-08-03 19:43:17 +00:00			`\| ^^^`
fix library and rustdoc tests 2023-04-16 11:12:37 +00:00			`\|`
			note: impl defined here, but it is not `const`
			`--> $SRC_DIR/alloc/src/vec/mod.rs:LL:COL`
			`= note: calls in constant functions are limited to constant functions, tuple structs and tuple variants`

liballoc: introduce String, Vec const-slicing This change `const`-qualifies many methods on Vec and String, notably `as_slice`, `as_str`, `len`. These changes are made behind the unstable feature flag `const_vec_string_slice` with the following tracking issue: https://github.com/rust-lang/rust/issues/129041 2024-07-30 13:48:36 +00:00			`error: aborting due to 1 previous error`
use impl substs in on_unimplemented 2022-03-07 02:38:42 +00:00
update tests, adding known-bug 2023-07-27 15:51:02 +00:00			For more information about this error, try `rustc --explain E0015`.