about summary refs log tree commit diff
path: root/src/test/ui/impl-trait
AgeCommit message (Collapse)AuthorLines
2020-04-08Redesign the Step traitCAD97-21/+5
2020-04-05Use smaller span for suggestion restricting lifetimeEsteban Küber-1/+1
2020-04-02tests: remove ignore directives from tests that mention core/alloc/std spans.Eduard-Mihai Burtescu-8/+3
2020-03-30Rollup merge of #70546 - lqd:polonius_update, r=nikomatsakisDylan DPC-2/+5
Polonius: update to 0.12.1, fix more move errors false positives, update test expectations This PR: - updates `polonius-engine` to version 0.12.1 to fix some move errors false positives - fixes a fact generation mistake creating the other move errors false positives - updates the test expectations for the polonius compare-mode so that all (minus the 2 OOMs) ui tests pass again (matching the [analysis doc](https://hackmd.io/CjYB0fs4Q9CweyeTdKWyEg?view) starting at case 34) In my opinion, this is safe to rollup. r? @nikomatsakis
2020-03-30bless output of ui test impl-trait/multiple-lifetimes/error-handling.rsRemy Rakic-2/+5
Some impl Trait fixes lead to locating more accurately the cause of a universal region error with a user annotation
2020-03-29Tweak `suggest_constraining_type_param`Esteban Küber-10/+8
Some of the bound restriction structured suggestions were incorrect while others had subpar output.
2020-03-22Store idents for `DefPathData` into crate metadataAaron Hill-0/+10
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-03-09Add FIXMEsYuki Okushi-6/+9
2020-03-09Add test for issue-67166Yuki Okushi-0/+22
2020-03-09Add test for issue-60473Yuki Okushi-0/+27
2020-03-09Add test for issue-57201Yuki Okushi-0/+22
2020-03-09Add test for issue-57200Yuki Okushi-0/+22
2020-03-06fix various typosMatthias Krüger-1/+1
2020-02-28keep predicate order and tweak outputEsteban Küber-21/+35
2020-02-28Tweak wordingEsteban Küber-7/+7
2020-02-28Mention the full path of the implementing traitEsteban Küber-7/+7
2020-02-28On single local candidate, use span labelEsteban Küber-14/+21
2020-02-19Tweak binding lifetime suggestion textEsteban Küber-2/+2
We already have a structured suggestion, but the wording made it seem like that wasn't the case. Fix #65286. r? @varkor
2020-02-14Fix and test nested impl TraitMatthew Jasper-0/+16
2020-02-14Update testsMatthew Jasper-19/+118
2020-02-14Handle equal regions in opaque type inferenceMatthew Jasper-0/+57
2020-02-14Update testsMatthew Jasper-46/+168
2020-02-14Call `is_freeze` less in unsafety-checkingMatthew Jasper-0/+32
This is to avoid cycles when calling `is_freeze` on an opaque type.
2020-02-14Explain a testMatthew Jasper-2/+9
2020-02-11Auto merge of #68929 - matprec:consistent-issue-references, r=Dylan-DPCbors-3/+3
Make issue references consistent Fixes https://github.com/rust-lang/rust/issues/62976 cc https://github.com/rust-lang/rust/pull/63008 r? @varkor because you reviewed the original pr
2020-02-09Auto merge of #67665 - Patryk27:master, r=zackmdavisbors-5/+10
Improve reporting errors and suggestions for trait bounds Fix #66802 - When printing errors for unsized function parameter, properly point at the parameter instead of function's body. - Improve `consider further restricting this bound` (and related) messages by separating human-oriented hints from the machine-oriented ones.
2020-02-09--bless --compare-mode=nllMatthias Prechtl-3/+3
2020-02-09Improve reporting errors and suggestions for trait boundsPatryk Wychowaniec-5/+10
2020-02-08review commentEsteban Küber-1/+1
2020-02-02Use more appropriate spans on object unsafe traits and provide structured ↵Esteban Küber-2/+8
suggestions when possible
2020-02-02Wording changes to object unsafe trait errorsEsteban Küber-2/+10
Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-02fix testEsteban Küber-4/+4
2020-02-02Rollup merge of #68760 - Tyg13:compile_fail_ui_test, r=CentrilMazdak Farrokhzad-5/+4
Issue error on `compile-fail` header in UI test Fixes #68732 r? @Centril
2020-02-02compiletest: error if `compile-fail` header in ui test.Tyler Lanphear-5/+4
2020-02-01Deduplicate generator interior typesJonas Schievink-2/+2
2020-01-24Apply `resolve_vars_if_possible` to returned types for more accurate suggestionsEsteban Küber-6/+6
2020-01-24Use more accurate return path spansEsteban Küber-25/+43
No longer suggest `Box::new(if foo { Type1 } else { Type2 })`, instead suggesting `if foo { Box::new(Type1) } else { Box::new(Type2) }`.
2020-01-23Account for `ty::Error` when suggesting `impl Trait` or `Box<dyn Trait>`Esteban Küber-2/+183
2020-01-16Account for object safety when suggesting `Box<dyn Trait>`Esteban Küber-2/+143
2020-01-16review commentsEsteban Küber-4/+11
2020-01-16review commentsEsteban Küber-0/+1
2020-01-16review commentsEsteban Küber-27/+13
2020-01-16Add E0746 explanation to the indexEsteban Küber-1/+1
2020-01-16When trait bounds are missing for return values, point at themEsteban Küber-2/+6
2020-01-16Elide E0308 errors in favor of E0746Esteban Küber-82/+10
When a type error involves a `dyn Trait` as the return type, do not emit the type error, as the "return type is not `Sized`" error will provide enough information to the user.
2020-01-16Account for diverging types in return `impl Trait`Esteban Küber-0/+5
2020-01-16Specific error for unsized `dyn Trait` return typeEsteban Küber-0/+222
Suggest `impl Trait` when possible, and `Box<dyn Trait>` otherwise.
2020-01-15wrap expr id into GeneratorInteriorTypeCausecsmoe-2/+2
2020-01-11Rollup merge of #68014 - estebank:unify-e0599, r=cramertjYuki Okushi-26/+26
Unify output of "variant not found" errors Fix #49566.
2020-01-10Rollup merge of #66463 - estebank:point-at-closure-and-opaque-types, r=CentrilMazdak Farrokhzad-0/+27
Point at opaque and closure type definitions in type errors Fixes #57266, fixes #67117.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 02:38:01 +0000