rust/src/test/ui/recursion/recursion.stderr, branch try

Move /src/test to /tests

2023-01-11T09:32:08+00:00

Make "long type" printing type aware

2022-11-18T16:42:59+00:00

Instead of simple string cutting, use a custom printer to hide parts of long printed types.

Let user see the full type of type-length limit error

2020-09-20T23:39:58+00:00

Better handling for exponential-sized types in misc places

2020-09-18T01:44:11+00:00

Mostly to fix ui/issues/issue-37311-type-length-limit/issue-37311.rs. Most parts of the compiler can handle deeply nested types with a lot of duplicates just fine, but some parts still attempt to naively traverse type tree. Before such problems were caught by type length limit check, but now these places will have to be changed to handle duplicated types gracefully.

Use smaller def span for functions

2020-08-22T22:41:49+00:00

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(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo(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.

Point at the call spawn when overflow occurs during monomorphization

2020-06-22T18:35:42+00:00

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`

Specify overflow checks behaviour in test

2020-02-11T19:35:29+00:00

rework run-fail and support check,build-fail

2019-12-21T21:16:00+00:00

Raise the default recursion limit to 128

2019-07-06T21:12:35+00:00

Update tests

2019-03-11T20:10:26+00:00