about summary refs log tree commit diff
path: root/src/test/ui/issues
AgeCommit message (Collapse)AuthorLines
2020-01-10Add ICE regression testsEsteban Küber-0/+44
2020-01-10Clarify suggestion for E0013varkor-9/+22
2020-01-10Introduce `#![feature(half_open_range_patterns)]`.Mazdak Farrokhzad-20/+91
This feature adds `X..`, `..X`, and `..=X` patterns.
2020-01-09Do not ICE on unicode next pointEsteban Küber-0/+23
Use `shrink_to_hi` instead of `next_point` Fix #68000.
2020-01-10Rollup merge of #66463 - estebank:point-at-closure-and-opaque-types, r=CentrilMazdak Farrokhzad-0/+2
Point at opaque and closure type definitions in type errors Fixes #57266, fixes #67117.
2020-01-09Update testsVadim Petrochenkov-33/+335
2020-01-09Rollup merge of #68023 - FSciammarella:master, r=Centril,varkorMazdak Farrokhzad-2/+2
Fix issue #68008 Correcting Typo on error message. From "substract" to "subtract". Fixes #68008.
2020-01-08Fix Typo on cannot "substract"Felipe Sciammarella-2/+2
Fix Typo on hir::BinOpKind::Sub "substract" to "subtract" Fix Typo on "Error cannot substract" Fix Typo on cannot "substract"
2020-01-08Explain that associated types and consts can't be accessed directly on the ↵Esteban Küber-1/+5
trait's path
2020-01-08review commentsEsteban Küber-1/+1
2020-01-08Point at opaque and closure type definitions in type errorsEsteban Küber-0/+2
2020-01-08Unify output of "variant not found" errorsEsteban Küber-75/+76
2020-01-08- remove syntax::{span_warn!, span_err!, span_fatal!. struct_err!}Mazdak Farrokhzad-33/+20
- remove syntax::{help!, span_help!, span_note!} - remove unused syntax::{struct_span_fatal, struct_span_err_or_warn!, span_err_or_warn!} - lintify check_for_bindings_named_same_as_variants + conflicting_repr_hints - inline syntax::{struct_span_warn!, diagnostic_used!} - stringify_error_code! -> error_code! & use it more. - find_plugin_registrar: de-fatalize an error - de-fatalize metadata errors - move type_error_struct! to rustc_typeck - struct_span_err! -> rustc_errors
2020-01-06fire "non_camel_case_types" for associated typesAndy Russell-0/+3
2020-01-06Use Self instead of $typeLzu Tao-2/+2
2020-01-05Add backticks to various diagnosticsvarkor-14/+14
2020-01-04Rollup merge of #67823 - euclio:drop-improvements, r=petrochenkovGuillaume Gomez-16/+10
improve some `Drop`-related error messages
2020-01-04Rollup merge of #67835 - euclio:delimiter-wording, r=CentrilMazdak Farrokhzad-8/+8
tweak wording of mismatched delimiter errors This PR improves the wording of the "incorrect delimiter" error messages. Here's a quick rationale: - *"un-closed" -> "unclosed"*: "unclosed" is valid English, so there's no need to hyphenate the prefix. This should be pretty uncontroversial, I think. - *"close delimiter" -> "closing delimiter"*: In my anecdotal experience, I've always heard "closing delimiter" or "closing parenthesis". In addition, the codebase already uses this terminology in comments and function names more than "close delimiter", which could indicate that it's more intuitive. - "incorrect delimiter" -> "mismatched delimiter": "Incorrect delimiter" is vague; why is it incorrect? "mismatched" clearly indicates why the delimiter is causing the error. r? @estebank
2020-01-03clarify that `Drop` can be implemented for enums and unions tooAndy Russell-2/+2
2020-01-03improve generic `Drop` error messagesAndy Russell-14/+8
- Use the span of the predicate - Use the def's description instead of "struct/enum" (notably incorrect for unions) - Align formatting with other error messages
2020-01-03tweak wording of mismatched delimiter errorsAndy Russell-8/+8
2020-01-03Implement uncommon_codepoints lint.Charles Lew-0/+1
2019-12-31Rollup merge of #67730 - Centril:typeck-pat-cleanup, r=estebankMazdak Farrokhzad-20/+28
Cleanup pattern type checking, fix diagnostics bugs (+ improvements) r? @estebank
2019-12-31Rollup merge of #67723 - ldm0:E0477, r=Dylan-DPCDylan DPC-0/+2
Add error code explanation for E0477 Part of #61137
2019-12-30Handle recursive instantiation of drop shimsMatthew Jasper-36/+0
2019-12-30refactor and fix this-expression-has-type noteMazdak Farrokhzad-2/+2
2019-12-30Pass the span of `<init>` in `let <pat> = <init>;`Mazdak Farrokhzad-4/+12
when type checking `<pat>`.
2019-12-30MatchExpressionArmPattern: Use more generic wording.Mazdak Farrokhzad-16/+16
The existing wording was inappropriate for e.g. `if let Ok(_) = expr { .. }`. The diagnostic would leak the fact that we desugar to a `match`.
2019-12-30Add error code explanation for E0477Donough Liu-0/+2
2019-12-30Rollup merge of #67677 - petrochenkov:dupexp, r=CentrilYuki Okushi-8/+8
resolve: Minor cleanup of duplicate macro reexports Enabled by https://github.com/rust-lang/rust/pull/65785 which changed `duplicate_macro_exports` from a lint to a hard error.
2019-12-29Auto merge of #67112 - Centril:expr-polish, r=estebankbors-6/+27
Refactor expression parsing thoroughly Based on https://github.com/rust-lang/rust/pull/66994 together with which this has refactored basically the entirety of `expr.rs`. r? @estebank
2019-12-28Ignore i586-unknown-linux-gnu and i586-unknown-musl in testsEsteban Küber-5/+11
2019-12-28resolve: Minor cleanup of duplicate macro reexportsVadim Petrochenkov-8/+8
2019-12-27Add regression test for old NLL ICERoss MacArthur-0/+20
2019-12-25Fix rebase and sort assoc type list for deterministic outputEsteban Küber-2/+2
2019-12-24Fix suggestion span for typo in associated type nameEsteban Küber-6/+6
2019-12-24Account for multiple trait bounds with missing associated typesEsteban Küber-3/+10
2019-12-24Avoid output dependency on std spansEsteban Küber-67/+60
2019-12-24Use structured suggestion for bad `Fn` traitsEsteban Küber-2/+1
2019-12-24Tweak errors for missing associated types and type parametersEsteban Küber-34/+66
2019-12-24Rollup merge of #67337 - oli-obk:no_mut_static_ref_from_const, r=RalfJungMazdak Farrokhzad-2/+10
Ensure that evaluating or validating a constant never reads from a static r? @RalfJung as per https://github.com/rust-lang/rust/pull/66302#issuecomment-554663387 This does not yet address the fact that evaluation of a constant can read from a static (under unleash-miri)
2019-12-23Auto merge of #66296 - Centril:bindings_after_at-init, r=pnkfelixbors-2/+2
Initial implementation of `#![feature(bindings_after_at)]` Following up on #16053, under the gate `#![feature(bindings_after_at)]`, `x @ Some(y)` is allowed subject to restrictions necessary for soundness. The implementation and test suite should be fairly complete now. One aspect that is not covered is the interaction with nested `#![feature(or_patterns)]`. This is not possible to test at the moment in a good way because that feature has not progressed sufficiently and has fatal errors in MIR building. We should make sure to add such tests before we stabilize both features (but shipping one of them is fine). r? @pnkfelix cc @nikomatsakis @matthewjasper @pcwalton cc https://github.com/rust-lang/rust/issues/65490
2019-12-23Rollup merge of #67538 - varkor:lhs-assign-diagnostics, r=CentrilMazdak Farrokhzad-15/+37
Improve diagnostics for invalid assignment - Improve wording and span information for invalid assignment diagnostics. - Link to https://github.com/rust-lang/rfcs/issues/372 when it appears the user is trying a destructuring assignment. - Make the equality constraint in `where` clauses error consistent with the invalid assignment error.
2019-12-23Constants reading or referencing statics is illegalOliver Scherer-1/+1
and some uses of it will be illegal forever (e.g. mutable or interior mutable statics)
2019-12-23Dynamically prevent constants from accessing staticsOliver Scherer-2/+10
2019-12-23check_legality_of_move_bindings: generalize diagnostics & add commentsMazdak Farrokhzad-2/+2
2019-12-23more recovery in if-parsingMazdak Farrokhzad-6/+27
2019-12-23Add span information to `ExprKind::Assign`varkor-6/+6
2019-12-23Improve invalid assignment errorvarkor-12/+34
2019-12-22Remove mem::uninitalized from testsMark Rousskov-8/+7
This purges uses of uninitialized where possible from test cases. Some are merely moved over to the equally bad pattern of MaybeUninit::uninit().assume_init() but with an annotation that this is "the best we can do".
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 03:47:37 +0000