3ed96a6d63
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` |
||
|---|---|---|
| .. | ||
| auxiliary | ||
| issue-26548-recursion-via-normalize.rs | ||
| issue-26548-recursion-via-normalize.stderr | ||
| issue-38591-non-regular-dropck-recursion.rs | ||
| issue-38591-non-regular-dropck-recursion.stderr | ||
| recursion.rs | ||
| recursion.stderr | ||
| recursive-enum.rs | ||
| recursive-enum.stderr | ||
| recursive-reexports.rs | ||
| recursive-reexports.stderr | ||
| recursive-requirements.rs | ||
| recursive-requirements.stderr | ||
| recursive-static-definition.rs | ||
| recursive-static-definition.stderr | ||
| recursive-types-are-not-uninhabited.rs | ||
| recursive-types-are-not-uninhabited.stderr | ||