about summary refs log tree commit diff
path: root/src/test/ui/issues
AgeCommit message (Collapse)AuthorLines
2018-11-06Rollup merge of #55700 - pnkfelix:issue-55533-update-ui-tests-wrt-nll, ↵kennytm-22/+34
r=davidtwco Update ui tests with respect to NLL Fix #55533
2018-11-06Rollup merge of #55694 - jsirs:issue-31076, r=oli-obkkennytm-0/+36
Fixes #31076
2018-11-06Rollup merge of #55664 - varkor:all-possible-cases-message, r=zackmdaviskennytm-2/+2
Make "all possible cases" help message uniform with existing help messages Specifically no capitalisation or trailing full stops.
2018-11-06Moved and renamed ui issue tests.Alexander Regueiro-41/+712
2018-11-05Remove `println!`'s from `ui/issues/issue-52126-assign-op-invariance.rs`Felix S. Klock II-5/+5
This is not strictly necessary to make this test "more robust with respect to NLL"; its just an attempt to narrow the scope of the test and focus on its core.
2018-11-05Make `ui/issues/issue-17263.rs` robust w.r.t. NLL.Felix S. Klock II-17/+29
2018-11-05add test for i32, fix incorrect locationjsirs-2/+10
2018-11-05update test to include concrete type (i32)jsirs-0/+2
2018-11-05Add testjsirs-0/+26
Add test for incompleately implemented add trait, see issue #31076
2018-11-04Ignore some more tests on emscriptenNikita Popov-1/+1
Either missing i128 or asm support
2018-11-04Auto merge of #55455 - estebank:expected-descr, r=michaelwoeristerbors-1/+1
Use token description in "expected/found" parse messages Fix #54309.
2018-11-03Make "all possible cases" help message uniform with existing help messagesvarkor-2/+2
Specifically no capitalisation or trailing full stops.
2018-11-01Put backticks around field names, types and paths in error messagesMichael Hewson-1/+1
Added to `DispatchFromDyn` and `CoerceUnsized` error messages
2018-10-29Don't emit cannot move errors twice in migrate modeMatthew Jasper-130/+10
2018-10-29Fix regressionEsteban Küber-2/+4
2018-10-29Rollup merge of #55423 - zackmdavis:back_out_bogus_ok_wrapping_suggestion, ↵Pietro Albini-33/+2
r=estebank back out bogus `Ok`-wrapping suggestion on `?` arm type mismatch This suggestion was introduced in #51938 / 6cc78bf8d7 (while introducing different language for type errors coming from `?` rather than a `match`), but it has a lot of false-positives, and incorrect suggestions carry more badness than marginal good suggestions do goodness. I regret not doing this earlier. :disappointed: Resolves #52537, resolves #54578. r? @estebank
2018-10-28Use token description in "expected/found" parse messagesEsteban Küber-5/+3
2018-10-28Rollup merge of #55199 - oli-obk:instance_printing, r=davidtwcokennytm-2/+2
Impl items have generics
2018-10-28Rollup merge of #55244 - wesleywiser:issue-50411, r=nikomatsakiskennytm-0/+11
Don't rerun MIR passes when inlining Fixes #50411 r? @nikomatsakis I updated your commit message with additional details. Let me know if any of that is incorrect. I also added the appropriate `compile-flags` directive to the test. Thanks for you help on this! cc @RalfJung related to your PR #55086
2018-10-28resolve: Desugar empty import groups into synthetic dummy importsVadim Petrochenkov-5/+5
so that they are correctly resolved on 2018 edition
2018-10-28resolve: More precise spans for privacy errorsVadim Petrochenkov-26/+26
2018-10-27back out bogus `Ok`-wrapping suggestion on `?` arm type mismatchZack M. Davis-33/+2
This suggestion was introduced in #51938 / 6cc78bf8d7 (while introducing different language for type errors coming from `?` rather than a `match`), but it has a lot of false-positives (as repeatedly reported in Issues #52537, #52598, #54578, #55336), and incorrect suggestions carry more badness than marginal good suggestions do goodness. Just get rid of it (unless and until someone figures out how to do it correctly). Resolves #52537, resolves #54578.
2018-10-27Auto merge of #55150 - ↵bors-3/+3
pnkfelix:issues-47215-54797-fix-ice-from-moving-out-of-thread-local-under-ast-borrowck, r=nikomatsakis Do not allow moving out of thread local under ast borrowck AST borrowck failed to prevent moving out of a thread-local static. This was broken. And it also (sometimes?) caused an ICE during drop elaboration. Fix #47215 Fix #54797
2018-10-26Auto merge of #55382 - kennytm:rollup, r=kennytmbors-6/+8
Rollup of 21 pull requests Successful merges: - #54816 (Don't try to promote already promoted out temporaries) - #54824 (Cleanup rustdoc tests with `@!has` and `@!matches`) - #54921 (Add line numbers option to rustdoc) - #55167 (Add a "cheap" mode for `compute_missing_ctors`.) - #55258 (Fix Rustdoc ICE when checking blanket impls) - #55264 (Compile the libstd we distribute with -Ccodegen-unit=1) - #55271 (Unimplement ExactSizeIterator for MIR traversing iterators) - #55292 (Macro diagnostics tweaks) - #55298 (Point at macro definition when no rules expect token) - #55301 (List allowed tokens after macro fragments) - #55302 (Extend the impl_stable_hash_for! macro for miri.) - #55325 (Fix link to macros chapter) - #55343 (rustbuild: fix remap-debuginfo when building a release) - #55346 (Shrink `Statement`.) - #55358 (Remove redundant clone (2)) - #55370 (Update mailmap for estebank) - #55375 (Typo fixes in configure_cmake comments) - #55378 (rustbuild: use configured linker to build boostrap) - #55379 (validity: assert that unions are non-empty) - #55383 (Use `SmallVec` for the queue in `coerce_unsized`.) - #55391 (bootstrap: clean up a few clippy findings)
2018-10-26Update testsOliver Scherer-2/+2
2018-10-26Rollup merge of #55298 - estebank:macro-def, r=pnkfelixkennytm-1/+4
Point at macro definition when no rules expect token Fix #35150.
2018-10-26Rollup merge of #55292 - estebank:macro-eof, r=pnkfelixkennytm-5/+4
Macro diagnostics tweaks Fix #30128, fix #10951 by adding an appropriate span to the diagnostic. Fix #26288 by suggesting adding semicolon to macro call.
2018-10-26Auto merge of #53821 - oli-obk:sanity_query, r=RalfJungbors-16/+50
Report const eval error inside the query Functional changes: We no longer warn about bad constants embedded in unused types. This relied on being able to report just a warning, not a hard error on that case, which we cannot do any more now that error reporting is consistently centralized. r? @RalfJung fixes #53561
2018-10-25Rebase falloutOliver Schneider-33/+4
2018-10-25update tests to changes on rustc masterOliver Schneider-6/+16
2018-10-25Deduplicate all the ~~things~~ errorsOliver Schneider-13/+16
2018-10-25Report const eval error inside the queryOliver Schneider-7/+57
2018-10-25Rollup merge of #55173 - estebank:suggest-static, r=oli-obkPietro Albini-6/+3
Suggest appropriate syntax on missing lifetime specifier in return type Suggest using `'static` when a lifetime is missing in the return type with a structured suggestion instead of a note. Fix #55170.
2018-10-24Point to macro def span instead of whole bodyEsteban Küber-6/+4
2018-10-23Point at macro definition when no rules expect tokenEsteban Küber-2/+7
2018-10-23Auto merge of #55229 - nikomatsakis:issue-54692-closure-signatures, ↵bors-7/+5
r=MatthewJasper enforce user annotations in closure signatures Not *quite* ready yet but I'm opening anyway. Still have to finish running tests locally. Fixes #54692 Fixes #54124 r? @matthewjasper
2018-10-23Modify invalid macro in expression context diagnosticEsteban Küber-5/+4
2018-10-23check the self type is well-formedNiko Matsakis-7/+5
This fixes `issue-28848.rs` -- it also handles another case that the AST region checker gets wrong (`wf-self-type.rs`). I don't actually think that this is the *right way* to be enforcing this constraint -- I think we should probably do it more generally, perhaps by editing `predicates_of` for the impl itself. The chalk-style implied bounds setup ought to fix this.
2018-10-23Auto merge of #55113 - mockersf:master, r=estebankbors-17/+401
#45829 when a renamed import conflict with a previous import Fix the suggestion when a renamed import conflict. It check if the snipped contains `" as "`, and if so uses everything before for the suggestion.
2018-10-23Auto merge of #54778 - scottmcm:stabilize-ihle, r=pnkfelixbors-56/+93
Stabilize impl_header_lifetime_elision in 2015 ~~This is currently blocked on https://github.com/rust-lang/rust/issues/54902; it should be good after that~~ It's already stable in 2018; this finishes the stabilization. FCP completed (https://github.com/rust-lang/rust/issues/15872#issuecomment-417953153), proposal (https://github.com/rust-lang/rust/issues/15872#issuecomment-412759783). Tracking issue: https://github.com/rust-lang/rust/issues/15872 Usage examples (from libcore): https://github.com/rust-lang/rust/pull/54687
2018-10-22Don't rerun Mir passes when inliningNiko Matsakis-0/+11
When inlining a function using the Mir inliner, we shouldn't rerun the various Mir passes on it because the Mir has already been lowered and that wil break various early Mir passes. The issue in #50411 is that we've inlined a function with promotions whose Mir has already been lowered. The promotions are then copied into the local function and we begin to run passes on their lowered Mir which causes the ICE. Fixes #50411
2018-10-22review commentsEsteban Küber-12/+3
2018-10-22Suggest appropriate syntax on missing lifetime specifier in return typeEsteban Küber-6/+12
Suggest using `'static` when a lifetime is missing in the return type with a structured suggestion instead of a note.
2018-10-21Auto merge of #55069 - matthewjasper:explain-free-region-liveness, ↵bors-205/+130
r=nikomatsakis [NLL] Use new region infer errors when explaining borrows Use the new free region infer errors for explaining borrows This gives at least some explanation for why a borrow is expected to last for a certain free region. Also: * Reports E0373: "closure may outlive the current function" with NLL. * Special cases the case of returning a reference to (or value referencing) a local variable or temporary (E0515). * Special case assigning a reference to a local variable in a closure to a captured variable. (E0521) Closes #51026 - `regions-nested-fns-2.rs` isn't changed to that diagnostic, since that would not be the correct error here. Closes #51169 cc #53882 - The error is (IMO) better now, but it could be better when we trace lifetimes in these error messages. r? @nikomatsakis cc @pnkfelix
2018-10-21Use new region infer errors for explaining borrowsMatthew Jasper-205/+130
This gives at least some explanation for why a borrow is expected to last for a certain free region. Also: * Reports E0373: "closure may outlive the current function" with NLL. * Special cases the case of returning a reference to (or value referencing) a local variable or temporary (E0515). * Special case assigning a reference to a local variable in a closure to a captured variable.
2018-10-21manage cases with tabs or other whitespacesFrançois Mockers-0/+160
2018-10-20Auto merge of #55156 - PramodBisht:issue/52717, r=estebankbors-13/+6
Fixed: Multiple errors on single typo in match pattern Here we have fixed the case where we were throwing two diagnostic messages `E0026` and `E0027` for same case. Example ``` error[E0026]: variant `A::A` does not have a field named `fob` --> src/test/ui/issue-52717.rs:20:12 | 20 | A::A { fob } => { println!("{}", fob); } | ^^^ variant `A::A` does not have this field error[E0027]: pattern does not mention field `foo` --> src/test/ui/issue-52717.rs:20:5 | 20 | A::A { fob } => { println!("{}", fob); } | ^^^^^^^^^^^^ missing field `foo` error: aborting due to 2 previous errors ``` Here above we can see that both `E0026` and `E0027` are depicting same thing. So, to fix this issue, we are simply checking if for last element of `inexistent_fields` is there any value lies in `unmentioned_fields` using levenshtein algorithm, if it does then for that case we are simply deleting element from `unmentioned_fields`. More or less, now instead of showing separate message in `E0027` we are giving extra hint on `E0026` r? @estebank
2018-10-1917905 also no longer errors, thanks to IHLEScott McMurray-12/+76
But its test was written in an outdated way that hits a different error despite IHLE, so keep a variant around for that case.
2018-10-19Hooray! 19982 finally works the way people wanted in December 2014 :)Scott McMurray-44/+17
2018-10-20Auto merge of #55007 - davidtwco:issue-39175, r=petrochenkovbors-0/+40
Help suggests non-existent package std::os::ext::process::CommandExt Fixes #39175.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-25 06:00:29 +0000