about summary refs log tree commit diff
path: root/src/test/ui/issues
AgeCommit message (Collapse)AuthorLines
2019-04-25Rollup merge of #60160 - xldenis:fix-overlapping-zero-width-annotation, ↵Mazdak Farrokhzad-3/+2
r=estebank Fix #58270, fix off-by-one error in error diagnostics. This fixes #58270 by checking if two diagnostics overlap completely when we're calculating the line offset for each message.
2019-04-24Rollup merge of #59739 - cramertj:stabilize, r=withoutboatsMazdak Farrokhzad-4/+4
Stabilize futures_api cc https://github.com/rust-lang/rust/issues/59725. Based on https://github.com/rust-lang/rust/pull/59733 and https://github.com/rust-lang/rust/pull/59119 -- only the last two commits here are relevant. r? @withoutboats , @oli-obk for the introduction of `rustc_allow_const_fn_ptr`.
2019-04-24Auto merge of #58623 - Amanieu:hashbrown3, r=alexcrichtonbors-3/+3
Replace HashMap implementation with SwissTable (as an external crate) This is the same as #56241 except that it imports `hashbrown` as an external crate instead of copying the implementation into libstd. This includes a few API changes (all unstable): - `try_reserve` is added to `HashSet`. - Some trait bounds have been changed in the `raw_entry` API. - `search_bucket` has been removed from the `raw_entry` API (doesn't work with SwissTable).
2019-04-23Stabilize futures_apiTaylor Cramer-4/+4
2019-04-24Fix testAmanieu d'Antras-3/+3
2019-04-23Rollup merge of #60169 - varkor:tidy-unnecessary-ignore-newline, r=kennytmMazdak Farrokhzad-35/+21
Warn when ignore-tidy-linelength is present, but no lines are too long It's easy for a `// ignore-tidy-linelength` to be added when there is a genuine need to ignore a file's line length, but then after refactoring the need is gone, but the tidy directive is not removed. This means that in the future, further editing may accidentally add unnecessarily long lines. This change forces `// ignore-tidy-linelength` to be used exactly when necessary, to make sure such changes are intentional.
2019-04-23Update ui testsvarkor-21/+21
2019-04-23Remove unnecessary ignore-tidy-linelengthvarkor-14/+0
2019-04-23Auto merge of #60125 - estebank:continue-evaluating, r=oli-obkbors-16/+71
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-23Auto merge of #60172 - varkor:tidy-double-trailing-newline, r=kennytmbors-18/+0
Disallow double trailing newlines in tidy This wasn't done previously in https://github.com/rust-lang/rust/pull/47064#issuecomment-354533010 as it affected too many files, but I think it's best to fix it now so that the number of files with double trailing newlines doesn't keep increasing. r? kennytm
2019-04-22Fix #58270, fix off-by-one error in error diagnostics.Xavier Denis-3/+2
2019-04-22Never stop due to errors before borrow checkingEsteban Küber-16/+71
2019-04-22Continue evaluating after item-type checkingEsteban Küber-2/+13
2019-04-22Remove double trailing newlinesvarkor-18/+0
2019-04-22update tests for migrate mode by defaultMatthew Jasper-1538/+446
2019-04-19Auto merge of #60073 - rchaser53:issue-60049, r=estebankbors-10/+55
avoid type-check body of DefId fix: #60049 related: PR #59798
2019-04-19avoid type-check body of DefIdrchaser53-10/+55
2019-04-19Rollup merge of #60064 - estebank:issue-59980, r=varkorMazdak Farrokhzad-3/+3
Point at try `?` on errors affecting the err match arm of the desugared code Fix #59980.
2019-04-19Rollup merge of #60061 - estebank:field-sugg, r=davidtwcoMazdak Farrokhzad-0/+37
Change suggestion of field when not in self context Fix #60057.
2019-04-19Rollup merge of #60052 - varkor:unused-parameter-diagnostic, r=estebankMazdak Farrokhzad-6/+6
Correct unused parameter diagnostic The message was incorrect for unused lifetime parameters. There's no need to be specific.
2019-04-18Suggest appropriate path when calling associated item on bare typesEsteban Küber-0/+4
When looking at the documentation for `std::f32` or `std::str`, for example, it is easy to get confused and assume `std::f32` and `f32` are the same thing. Because of this, it is not uncommon to attempt writing `f32::consts::PI` instead of the correct `std::f32::consts::PI`. When encountering the former, which results in an access error due to it being an inexistent path, try to access the same path under `std`. If this succeeds, this information is stored for later tweaking of the final E0599 to provide an appropriate suggestion. This suggestion applies to both E0233 and E0599 and is only checked when the first ident of a path corresponds to a primitive type.
2019-04-18Fix rebaseEsteban Küber-1/+1
2019-04-18review comments: change wordingEsteban Küber-1/+1
2019-04-18Change suggestion of field when not in self contextEsteban Küber-0/+37
2019-04-18Update testsvarkor-6/+6
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-108/+70
2019-04-18Auto merge of #60048 - estebank:issue-54954, r=sanxiynbors-0/+35
Fix ICE on const evaluation of const method Fix #54954.
2019-04-18Auto merge of #60051 - estebank:fn-sugg, r=davidtwcobors-13/+7
Do not mention missing `PartialOrd` impl when involving uncalled fns
2019-04-17Give custom error for E0277 on `?` error caseEsteban Küber-1/+1
2019-04-17Point at try `?` on errors affecting the err match arm of the desugared codeEsteban Küber-2/+2
2019-04-17Do not mention missing `PartialOrd` impl when involving uncalled fnsEsteban Küber-13/+7
2019-04-17Fix ICE on const evaluation of const methodEsteban Küber-0/+35
2019-04-17Resolve inconsistency in error messages between "parameter" and "variable".Eduard-Mihai Burtescu-5/+5
2019-04-16Auto merge of #59769 - RalfJung:compiletest-normalization, r=alexcrichtonbors-0/+12
compiletest normalization: preserve non-JSON lines such as ICEs Currently, every non-JSON line from stderr gets normalized away when compiletest normalizes the output. In particular, ICEs get normalized to the empty output. That does not seem desirable, so this changes normalization to preserve non-JSON lines instead. Also see https://github.com/laumann/compiletest-rs/issues/169: because of that bug, Miri currently *looks* green in the toolstate, but some tests ICE. That same bug is likely no longer present in latest compiletest because the error code gets checked separately, but it still seems like a good idea to also make sure that ICEs are considered stderr output: This change found an accidental user-visible `error!` in CTFE validation (fixed), and a non-deterministic panic when there are two `main` symbols (not fixed, no idea where this comes from). Both got missed before because non-JSON output got ignored.
2019-04-14Rollup merge of #59896 - estebank:dedup-spans, r=davidtwcoMazdak Farrokhzad-0/+27
Remove duplicated redundant spans Fix #59895.
2019-04-14some more tests need normalizationRalf Jung-0/+4
2019-04-14normalize away spurious errorRalf Jung-0/+8
2019-04-14Auto merge of #59798 - rchaser53:issue-59488, r=estebankbors-0/+107
Improvement for comparision against fn I try to add error message. related: https://github.com/rust-lang/rust/issues/59488
2019-04-12Add test and fix dedupEsteban Küber-0/+27
2019-04-12Rollup merge of #59862 - estebank:tweak-unstable-diag, r=petrochenkovMazdak Farrokhzad-12/+24
Tweak unstable diagnostic output
2019-04-12Rollup merge of #59859 - davidtwco:issue-59756, r=cramertjMazdak Farrokhzad-1/+4
Suggest removing `?` to resolve type errors. Fixes #59756.
2019-04-12Rollup merge of #59846 - euclio:not-a-module, r=davidtwcoMazdak Farrokhzad-10/+7
clarify what the item is in "not a module" error The motivation here was that I was trying to import an associated constant when I thought it was an enum variant, and got confused by this error. Ideally I would like to add a note saying that associated constants, types, and methods cannot be imported, but I'm not sure that the associated items for a `Def` can be checked at resolve time.
2019-04-12Rollup merge of #59781 - whitfin:issue-59378, r=oli-obkMazdak Farrokhzad-12/+3
Remove check_match from const_eval This fixes #59378. It seems that the `check_match` may be unnecessary, so this removes it per instructions provided in the issue. I re-ran the tests for `librustc_mir` and everything seemed fine!
2019-04-12add the logic for when other_ty is FnDefrchaser53-3/+47
2019-04-11Reword tracking issue noteEsteban Küber-12/+12
2019-04-12improve error messagesrchaser53-7/+37
2019-04-10Tweak unstable diagnostic outputEsteban Küber-12/+24
2019-04-10Suggest removing `?` to resolve type errors.David Wood-1/+4
This commit adds a suggestion to remove the `?` from expressions if removing the `?` would resolve a type error.
2019-04-10clarify what the item is in "not a module" errorAndy Russell-10/+7
2019-04-09improve unknown enum variant errorsAndy Russell-41/+36
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 23:36:00 +0000