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

// Verify the compiler fails with an error on infinite function
// recursions.

//@ build-fail
//@ normalize-stderr-test: ".nll/" -> "/"

fn generic<T>() { //~ WARN function cannot return without recursing
    generic::<Option<T>>();
}
//~^^ ERROR reached the recursion limit while instantiating `generic::<Option<


fn main () {
    // Use generic<T> at least once to trigger instantiation.
    generic::<i32>();
}
Ensure an error is raised on infinite recursion 2014-02-13 20:19:03 +00:00			`// Verify the compiler fails with an error on infinite function`
			`// recursions.`

rework run-fail and support check,build-fail 2019-12-14 03:28:32 +00:00			`//@ build-fail`
Let user see the full type of type-length limit error 2020-09-16 02:45:58 +00:00			`//@ normalize-stderr-test: ".nll/" -> "/"`
rework run-fail and support check,build-fail 2019-12-14 03:28:32 +00:00
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-22 02:32:35 +00:00			`fn generic<T>() { //~ WARN function cannot return without recursing`
Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 15:29:52 +00:00			`generic::<Option<T>>();`
Test fixes and rebase conflicts from rollups PRs closed as part of this: Closes #12212 r=alexcrichton Closes #12215 r=brson Closes #12246 r=pcwalton Closes #12247 r=cmr Closes #12251 r=brson Closes #12255 r=alexcrichton Closes #12257 r=alexcrichton Closes #12258 r=huonw Closes #12259 r=huonw Closes #12263 r=kballard Closes #12269 r=alexcrichton 2014-02-14 16:42:23 +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			//~^^ ERROR reached the recursion limit while instantiating `generic::<Option<
Ensure an error is raised on infinite recursion 2014-02-13 20:19:03 +00:00

			`fn main () {`
			`// Use generic<T> at least once to trigger instantiation.`
Fallout: tests. As tests frequently elide things, lots of changes here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test. 2015-02-12 15:29:52 +00:00			`generic::<i32>();`
Ensure an error is raised on infinite recursion 2014-02-13 20:19:03 +00:00			`}`