about summary refs log tree commit diff
path: root/src/test/ui/issues
AgeCommit message (Collapse)AuthorLines
2019-11-10Make error and warning annotations mandatory in UI testsTomasz Miąsko-23/+13
This change makes error and warning annotations mandatory in UI tests. The only exception are tests that use error patterns to match compiler output and don't have any annotations.
2019-11-10Improve coherence errors for wrong type orderOhad Ravid-0/+1
2019-11-10Undo an assert causing an ICE until we fix the problem properlyOliver Scherer-0/+15
2019-11-08Rollup merge of #66007 - estebank:remove-here, r=CentrilMazdak Farrokhzad-16/+16
Remove "here" from "expected one of X here"
2019-11-08Rollup merge of #65785 - Centril:compat-to-error-2, r=oli-obkMazdak Farrokhzad-131/+59
Transition future compat lints to {ERROR, DENY} - Take 2 Follow up to https://github.com/rust-lang/rust/pull/63247 implementing https://github.com/rust-lang/rust/pull/63247#issuecomment-536295992. - `legacy_ctor_visibility` (ERROR) -- closes #39207 - `legacy_directory_ownership` (ERROR) -- closes #37872 - `safe_extern_static` (ERROR) -- closes #36247 - `parenthesized_params_in_types_and_modules` (ERROR) -- closes #42238 - `duplicate_macro_exports` (ERROR) - `nested_impl_trait` (ERROR) -- closes #59014 - `ill_formed_attribute_input` (DENY) -- transitions #57571 - `patterns_in_fns_without_body` (DENY) -- transitions #35203 r? @varkor cc @petrochenkov
2019-11-08Suggest `#[repr(C)]` instead of `#[repr(C, packed, ...)]`PotHix-2/+2
The code was previously suggesting `#[repr(C, packed, ...)]` for incorrect uses of `repr` (e.g. `#[repr = "C"]`). This change suggests the usage of `#[repr(C)]` instead. r? @estebank ref #61286
2019-11-08Rollup merge of #66049 - RalfJung:missing-spans, r=alexcrichtonYuki Okushi-7/+5
consistent handling of missing sysroot spans Due to https://github.com/rust-lang/rust/issues/53081, sysroot spans (pointing to code in libcore/libstd/...) fails to print on some x86 runners. This consolidates the ignore directives for that and references the relevant issue. I also did that for the generated derive-error-span tests -- but there the script and the tests were not entirely in sync any more since https://github.com/rust-lang/rust/pull/64151. Cc @estebank @varkor
2019-11-07Rollup merge of #66087 - tmiasko:ui-mode, r=CentrilMazdak Farrokhzad-266/+262
Update some build-pass ui tests to use check-pass where applicable Helps with issue https://github.com/rust-lang/rust/issues/62277.
2019-11-07Rollup merge of #63793 - oli-obk:🧹, r=dtolnayMazdak Farrokhzad-6/+4
Have tidy ensure that we document all `unsafe` blocks in libcore cc @rust-lang/libs I documented a few and added ignore flags on the other files. We can incrementally document the files, but won't regress any files this way.
2019-11-07Update ui testsGuillaume Gomez-1/+2
2019-11-07Use -Zsave-analysis when compiling issue-37323.rsTomasz Miąsko-0/+1
2019-11-06Remove "here" from "expected one of X here"Esteban Küber-16/+16
2019-11-06Suggest missing item from `trait` in `impl`Esteban Küber-1/+1
2019-11-06Auto merge of #65134 - davidtwco:issue-19834-improper-ctypes-in-extern-C-fn, ↵bors-0/+6
r=rkruppe improper_ctypes: `extern "C"` fns cc #19834. Fixes #65867. This pull request implements the change [described in this comment](https://github.com/rust-lang/rust/issues/19834#issuecomment-466671572). cc @rkruppe @varkor @shepmaster
2019-11-06duplicate_macro_exports -> errorMazdak Farrokhzad-33/+0
2019-11-06parenthesized_params_in_types_and_modules -> errorMazdak Farrokhzad-76/+32
2019-11-06safe_extern_static -> errorMazdak Farrokhzad-22/+27
2019-11-06Rebase falloutOliver Scherer-6/+4
2019-11-06Rollup merge of #66054 - petrochenkov:delspan, r=estebankMazdak Farrokhzad-1/+1
syntax: Avoid span arithmetic for delimiter tokens The +/-1 logic is from the time where the whole group had a single span and the delimiter spans had to be calculated from it. Now the delimiters have their own spans which are constructed by lexer or proc macro API and can be used directly. If those spans are not perfect, then it should be fixed by tweaking the corresponding lexer logic rather than by trying to add or substract `1` from the span boundaries. Fixes https://github.com/rust-lang/rust/issues/62524 r? @estebank
2019-11-06Rollup merge of #66014 - dkadashev:47319-type-param-def-location, r=estebankMazdak Farrokhzad-8/+20
Show type parameter name and definition in type mismatch error messages Fixes #47319 r? estebank
2019-11-06Apply review suggestionsTomasz Miąsko-6/+6
2019-11-05improper_ctypes: `extern "C"` fnsDavid Wood-0/+6
2019-11-04Add warning annotations for issue-47094 testTomasz Miąsko-2/+2
2019-11-04Use check-pass in ui tests where appropriateTomasz Miąsko-210/+209
2019-11-04Use build-pass in ui tests where appropriateTomasz Miąsko-48/+48
2019-11-04Use run-pass for ui tests where appropriateTomasz Miąsko-2/+2
2019-11-04Remove no longer useful ui testTomasz Miąsko-4/+0
2019-11-04Auto merge of #65838 - estebank:resilient-recovery, r=Centrilbors-16/+3
Reduce amount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it on a more granular way in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. Fix #63690.
2019-11-03syntax: Avoid span arithmetics for delimiter tokensVadim Petrochenkov-1/+1
2019-11-02consistent handling of missing sysroot spansRalf Jung-7/+5
2019-11-02Update error annotations in tests that successfully compileTomasz Miąsko-1/+0
Those annotation are silently ignored rather than begin validated against compiler output. Update them before validation is enabled, to avoid test failures.
2019-11-02Update testsDmitry Kadashev-8/+20
Update the tests to reflect changes to how type mismatch errors are reported (two previous commits).
2019-10-31Fix incorrect diagnostics for expected type in E0271 with an associated typeOhad Ravid-3/+3
2019-10-30Reduce ammount of errors given unclosed delimiterEsteban Küber-16/+3
When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace.
2019-10-29Rollup merge of #65832 - tlively:emscripten-exception-handling, r=alexcrichtonTyler Mandry-4/+4
Re-enable Emscripten's exception handling support Passes LLVM codegen and Emscripten link-time flags for exception handling if and only if the panic strategy is `unwind`. Sets the default panic strategy for Emscripten targets to `unwind`. Re-enables tests that depend on unwinding support for Emscripten, including `should_panic` tests. r? @alexcrichton
2019-10-29Rollup merge of #65562 - Patryk27:master, r=estebankMazdak Farrokhzad-4/+4
Improve the "try using a variant of the expected type" hint. Fix https://github.com/rust-lang/rust/issues/65494. - Change type-printing output. - Use `span_to_snippet` when possible. - Change the message to `try using a variant of the expected enum`
2019-10-29Rollup merge of #65318 - estebank:coherence, r=varkorMazdak Farrokhzad-2/+2
Call out the types that are non local on E0117 CC #24745.
2019-10-29Rollup merge of #65294 - varkor:lint-inline-prototype, r=matthewjasperMazdak Farrokhzad-0/+8
Lint ignored `#[inline]` on function prototypes Fixes https://github.com/rust-lang/rust/issues/51280. - Adds a `unused_attribute` lint for `#[inline]` on function prototypes. - As a consequence, foreign items, impl items and trait items now have their attributes checked, which could cause some code to no longer compile (it was previously erroneously ignored).
2019-10-28Rollup merge of #65640 - estebank:recover-missing-semi, r=CentrilMazdak Farrokhzad-1/+1
Use heuristics to recover parsing of missing `;` - Detect `,` and `:` typos where `;` was intended. - When the next token could have been the start of a new statement, detect a missing semicolon. Fix #48160, fix #44767 (after adding note about statements).
2019-10-28Tweak unexpected token wordingEsteban Küber-1/+1
2019-10-28Improve the "try using a variant of the expected type" hint.Patryk Wychowaniec-4/+4
2019-10-28Use more targeted spans for orphan rule errorsEsteban Küber-2/+2
2019-10-27Point at local similarly named element and tweak references to variantsEsteban Küber-65/+96
Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-27update testsMark Mansi-0/+14
2019-10-27Auto merge of #65288 - estebank:point-at-assoc-type, r=nikomatsakisbors-6/+12
Point at associated type for some obligations Partially address #57663.
2019-10-26Rollup merge of #65773 - estebank:sugg-whitespace, r=CentrilMazdak Farrokhzad-0/+46
Increase spacing for suggestions in diagnostics Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages. r? @Centril
2019-10-25Emit warning for ignored #[inline] on trait method prototypesvarkor-0/+8
2019-10-25Re-enable Emscripten's exception handling supportThomas Lively-4/+4
Passes LLVM codegen and Emscripten link-time flags for exception handling if and only if the panic strategy is `unwind`. Sets the default panic strategy for Emscripten targets to `unwind`. Re-enables tests that depend on unwinding support for Emscripten, including `should_panic` tests.
2019-10-25Rollup merge of #65390 - GuillaumeGomez:long-err-explanation-E0576, ↵Mazdak Farrokhzad-0/+3
r=matthewjasper,kinnison Add long error explanation for E0576 Part of #61137.
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+46
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 20:47:53 +0000