summary refs log tree commit diff
path: root/src/test/ui/recursion
AgeCommit message (Collapse)AuthorLines
2020-06-30Bless failing testsLeSeulArtichaut-2/+6
2020-06-22Point at the call spawn when overflow occurs during monomorphizationAaron Hill-5/+27
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-15Rollup merge of #72879 - RalfJung:miri-tctx-at, r=oli-obkRalf Jung-2/+2
Miri: avoid tracking current location three times Miri tracks the current instruction to execute in the call stack, but it also additionally has two `TyCtxtAt` that carry a `Span` that also tracks the current instruction. That is quite silly, so this PR uses `TyCtxt` instead, and then uses a method for computing the current span when a `TyCtxtAt` is needed. Having less redundant (semi-)global state seems like a good improvement to me. :D To keep the ConstProp errors the same, I had to add the option to `error_to_const_error` to overwrite the span. Also for some reason this changes cycle errors a bit -- not sure if we are now better or worse as giving those queries the right span. (It is unfortunately quite easy to accidentally use `DUMMY_SP` by calling the query on a `TyCtxt` instead of a `TyCtxtAt`.) r? @oli-obk @eddyb
2020-06-12fix const_prop spans and re-bless testsRalf Jung-2/+2
2020-06-10review comments: only suggest one substitutionEsteban Küber-5/+1
2020-06-10On recursive ADT, provide indirection structured suggestionEsteban Küber-1/+8
2020-05-31Add descriptions for all queriesMatthew Jasper-5/+10
2020-04-08Small tweaks to required bound spanEsteban Küber-2/+2
2020-04-08Use `PredicateObligation`s instead of `Predicate`sEsteban Küber-2/+2
Keep more information about trait binding failures.
2020-04-02tests: remove ignore directives from tests that mention core/alloc/std spans.Eduard-Mihai Burtescu-6/+1
2020-03-27non-exhastive diagnostic: add note re. scrutinee typeMazdak Farrokhzad-0/+1
2020-03-23Ignore tests on some platforms due to #53081Aaron Hill-1/+6
2020-03-22Store idents for `DefPathData` into crate metadataAaron Hill-0/+5
Previously, we threw away the `Span` associated with a definition's identifier when we encoded crate metadata, causing us to lose location and hygiene information. We now store the identifier's `Span` in the crate metadata. When we decode items from the metadata, we combine the name and span back into an `Ident`. This improves the output of several tests, which previously had messages suppressed due to dummy spans. This is a prerequisite for #68686, since throwing away a `Span` means that we lose hygiene information.
2020-02-12Auto merge of #68679 - matthewjasper:needs-type-op, r=varkorbors-1/+2
Improve `ty.needs_drop` * Handle cycles in `needs_drop` correctly * Normalize types when computing `needs_drop` * Move queries from rustc to rustc_ty * Avoid query in simple cases reopens #65918
2020-02-11Specify overflow checks behaviour in testMatthew Jasper-1/+2
2020-02-01Update existing tests for or-patternsMatthew Jasper-10/+2
2020-01-19fix real_drop_in_place in commentsRalf Jung-1/+1
2020-01-18adjust ui testsRalf Jung-1/+1
2019-12-30Handle recursive instantiation of drop shimsMatthew Jasper-0/+47
2019-12-21rework run-fail and support check,build-failMazdak Farrokhzad-1/+3
2019-10-09Suggest `if let` on `let` refutable bindingEsteban Küber-0/+7
2019-09-06Fixed grammar/style in error messages and reblessed tests.Alexander Regueiro-3/+3
2019-08-31Use span label instead of note for cause in E0631Esteban Küber-10/+6
2019-08-10diagnostics: Describe crate root modules in `DefKind::Mod` as "crate"Vadim Petrochenkov-2/+2
2019-08-05Make use of possibly uninitialized data a hard errorTyler Mandry-25/+3
This is one of the behaviors we no longer allow in NLL. Since it can lead to undefined behavior, I think it's definitely worth making it a hard error without waiting to turn off migration mode (#58781). Closes #60450. My ulterior motive here is making it impossible to leave variables partially initialized across a yield (see discussion at #63035), so tests are included for that.
2019-07-07Raise the default recursion limit to 128Simonas Kazlauskas-1/+1
2019-05-21Add FAQ for NLL migrationJethro Beekman-0/+1
2019-05-12Change compare mode to use -Zborrowck=mirMatthew Jasper-0/+16
2019-04-23Auto merge of #60125 - estebank:continue-evaluating, r=oli-obkbors-1/+14
Don't stop evaluating due to errors before borrow checking r? @oli-obk Fix #60005. Follow up to #59903. Blocked on #53708, fixing the ICE in `src/test/ui/consts/match_ice.rs`.
2019-04-22Never stop due to errors before borrow checkingEsteban Küber-1/+14
2019-04-22Remove double trailing newlinesvarkor-1/+0
2019-03-11Update testsVadim Petrochenkov-2/+2
2018-12-25Remove licensesMark Rousskov-81/+11
2018-12-24make non_camel_case_types an early lintAndy Russell-5/+5
2018-10-25Deduplicate all the ~~things~~ errorsOliver Schneider-0/+5
2018-10-25Report const eval error inside the queryOliver Schneider-0/+5
2018-09-30Deduplicate errors in the obligation forest.Diogo Sousa-8/+28
Fixes #40827.
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+212