rust/src/test/ui/recursion/recursion.rs, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2023-01-11T09:32:08+00:00Move /src/test to /tests2023-01-11T09:32:08+00:00Albert Larsan74931857+albertlarsan68@users.noreply.github.com2023-01-05T08:13:28+00:00urn:sha1:cf2dff2b1e3fa55fa5415d524200070d0d7aacfeLet user see the full type of type-length limit error2020-09-20T23:39:58+00:00Kornel Lesińskikornel@geekhood.net2020-09-16T02:45:58+00:00urn:sha1:34d3c7df80dc687e184d8bfa456e851cad9839dePoint at the call spawn when overflow occurs during monomorphization2020-06-22T18:35:42+00:00Aaron Hillaa1ronham@gmail.com2020-06-22T02:32:35+00:00urn:sha1:3ed96a6d638f8dc8aa081ca1ad82e61caa8930ca
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 test2020-02-11T19:35:29+00:00Matthew Jaspermjjasper1@gmail.com2020-02-10T22:31:19+00:00urn:sha1:30a8353f372f7cc719d1de6811996ce5215183a6rework run-fail and support check,build-fail2019-12-21T21:16:00+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-12-14T03:28:32+00:00urn:sha1:b4420c8f5c9be977b72b9b0027800ae36aa0f302Remove licenses2018-12-26T04:08:33+00:00Mark Rousskovmark.simulacrum@gmail.com2018-12-25T15:56:47+00:00urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718cMerged migrated compile-fail tests and ui tests. Fixes #46841.2018-08-14T09:12:09+00:00David Wooddavid@davidtw.co2018-08-08T12:50:16+00:00urn:sha1:3fc7ab237314a4ce85e612b4ce590c27f1425291