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

warning: function cannot return without recursing
  --> $DIR/issue-8727.rs:7:1
   |
LL | fn generic<T>() {
   | ^^^^^^^^^^^^^^^ cannot return without recursing
LL |     generic::<Option<T>>();
   |     ---------------------- recursive call site
   |
   = help: a `loop` may express intention better if this is on purpose
   = note: `#[warn(unconditional_recursion)]` on by default

error: reached the recursion limit while instantiating `generic::<Option<Option<Option<Option<Option<...>>>>>>`
  --> $DIR/issue-8727.rs:8:5
   |
LL |     generic::<Option<T>>();
   |     ^^^^^^^^^^^^^^^^^^^^^^
   |
note: `generic` defined here
  --> $DIR/issue-8727.rs:7:1
   |
LL | fn generic<T>() {
   | ^^^^^^^^^^^^^^^
   = note: the full type name has been written to '$TEST_BUILD_DIR/issues/issue-8727/issue-8727.long-type.txt'

error: aborting due to previous error; 1 warning emitted
librustc_lint: In recursion warning, change 'recurring' to 'recursing' 2018-08-20 23:09:15 -07:00			`warning: function cannot return without recursing`
Let user see the full type of type-length limit error 2020-09-16 03:45:58 +01:00			`--> $DIR/issue-8727.rs:7:1`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| fn generic<T>() {`
librustc_lint: In recursion warning, change 'recurring' to 'recursing' 2018-08-20 23:09:15 -07:00			`\| ^^^^^^^^^^^^^^^ cannot return without recursing`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`LL \| generic::<Option<T>>();`
			`\| ---------------------- recursive call site`
			`\|`
			= help: a `loop` may express intention better if this is on purpose
bless ui tests 2022-09-18 19:55:36 +04:00			= note: `#[warn(unconditional_recursion)]` on by default
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
Make "long type" printing type aware Instead of simple string cutting, use a custom printer to hide parts of long printed types. 2022-11-15 17:38:39 -08:00			error: reached the recursion limit while instantiating `generic::<Option<Option<Option<Option<Option<...>>>>>>`
Let user see the full type of type-length limit error 2020-09-16 03:45:58 +01:00			`--> $DIR/issue-8727.rs:8:5`
Point at the call spawn when overflow occurs during monomorphization This improves the output for issue #72577, but there's still more work to be done. Currently, an overflow error during monomorphization results in an error that points at the function we were unable to monomorphize. However, we don't point at the call that caused the monomorphization to happen. In the overflow occurs in a large recursive function, it may be difficult to determine where the issue is. This commit tracks and `Span` information during collection of `MonoItem`s, which is used when emitting an overflow error. `MonoItem` itself is unchanged, so this only affects `src/librustc_mir/monomorphize/collector.rs` 2020-06-21 22:32:35 -04:00			`\|`
			`LL \| generic::<Option<T>>();`
			`\| ^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
			note: `generic` defined here
Let user see the full type of type-length limit error 2020-09-16 03:45:58 +01:00			`--> $DIR/issue-8727.rs:7:1`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata. 2020-08-12 17:02:14 -04:00			`LL \| fn generic<T>() {`
			`\| ^^^^^^^^^^^^^^^`
Let user see the full type of type-length limit error 2020-09-16 03:45:58 +01:00			`= note: the full type name has been written to '$TEST_BUILD_DIR/issues/issue-8727/issue-8727.long-type.txt'`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
rustc: Add a warning count upon completion 2020-03-11 16:30:09 +01:00			`error: aborting due to previous error; 1 warning emitted`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00