rust/tests/ui/issues/issue-17651.stderr

error[E0277]: the size for values of type `[{integer}]` cannot be known at compilation time
  --> $DIR/issue-17651.rs:5:18
   |
LL |     (|| Box::new(*(&[0][..])))();
   |         -------- ^^^^^^^^^^^ doesn't have a size known at compile-time
   |         |
   |         required by a bound introduced by this call
   |
   = help: the trait `Sized` is not implemented for `[{integer}]`
note: required by a bound in `Box::<T>::new`
  --> $SRC_DIR/alloc/src/boxed.rs:LL:COL

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			error[E0277]: the size for values of type `[{integer}]` cannot be known at compilation time
			`--> $DIR/issue-17651.rs:5:18`
			`\|`
			`LL \| (\|\| Box::new(*(&[0][..])))();`
Point at call span that introduced obligation for the arg 2021-09-07 11:30:53 +00:00			`\| -------- ^^^^^^^^^^^ doesn't have a size known at compile-time`
			`\| \|`
			`\| required by a bound introduced by this call`
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			= help: the trait `Sized` is not implemented for `[{integer}]`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-05 23:04:09 +00:00			note: required by a bound in `Box::<T>::new`
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition 2021-07-17 18:13:50 +00:00			`--> $SRC_DIR/alloc/src/boxed.rs:LL:COL`
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00
Point at argument when evaluating `Path`'s bounds When evaluating an `ExprKind::Call`, we first have to `check_expr` on it's callee. When this one is a `ExprKind::Path`, we had to evaluate the bounds introduced for its arguments, but by the time we evaluated them we no longer had access to the argument spans. Now we special case this so that we can point at the right place on unsatisfied bounds. This also allows the E0277 deduplication to kick in correctly, so we now emit fewer errors. 2021-09-14 10:52:36 +00:00			`error: aborting due to previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0277`.