about summary refs log tree commit diff
path: root/src/test/ui/traits
AgeCommit message (Collapse)AuthorLines
2020-04-22Sort `MultiSpan`s on creationEsteban Küber-1/+1
2020-04-18Add label to item source of bound obligationEsteban Küber-1/+1
2020-04-18Do not emit note for projected derived obligationsEsteban Küber-1/+0
2020-04-18Remove `AssocTypeBound` and propagate bound `Span`sEsteban Küber-15/+11
2020-04-18Maintain chain of derived obligationsEsteban Küber-0/+5
When evaluating the derived obligations from super traits, maintain a reference to the original obligation in order to give more actionable context in the output.
2020-04-14Rename AssocKind::Method to AssocKind::FnRustin-Liu-2/+2
Rename fn_has_self_argument to fn_has_self_parameter Rename AssocItemKind::Method to AssocItemKind::Fn Refine has_no_input_arg Refine has_no_input_arg Revert has_no_input_arg Refine suggestion_descr Move as_def_kind into AssocKind Signed-off-by: Rustin-Liu <rustin.liu@gmail.com> Fix tidy check issue Signed-off-by: Rustin-Liu <rustin.liu@gmail.com>
2020-04-11rustc: Add a warning count upon completionRoccoDev-1/+1
2020-04-08Small tweaks to required bound spanEsteban Küber-25/+25
2020-04-08Use `PredicateObligation`s instead of `Predicate`sEsteban Küber-17/+26
Keep more information about trait binding failures.
2020-04-05"cannot resolve" → "cannot satisfy"Esteban Küber-1/+1
2020-04-03Rollup merge of #70741 - DutchGhost:test-59023, r=CentrilMazdak Farrokhzad-0/+17
Add test for #59023 Adds a test for https://github.com/rust-lang/rust/issues/59023 Closes https://github.com/rust-lang/rust/issues/59023
2020-04-03Add test for #59023DutchGhost-0/+17
2020-04-02tests: remove ignore directives from tests that mention core/alloc/std spans.Eduard-Mihai Burtescu-18/+9
2020-03-29Tweak `suggest_constraining_type_param`Esteban Küber-24/+18
Some of the bound restriction structured suggestions were incorrect while others had subpar output.
2020-03-26add test for negative specializes negativeNiko Matsakis-0/+13
2020-03-26move stderr file tooNiko Matsakis-0/+12
2020-03-26give the negative-impls-builtin test a more sensible nameNiko Matsakis-0/+0
2020-03-26comment the `typeck-negative-impls-builtin` testNiko Matsakis-0/+3
2020-03-26move feature-gate-negative-impls test to traits/negative-implsNiko Matsakis-0/+3
2020-03-26introduce `negative_impls` feature gate and documentNiko Matsakis-18/+47
They used to be covered by `optin_builtin_traits` but negative impls are now applicable to all traits, not just auto traits. This also adds docs in the unstable book for the current state of auto traits.
2020-03-26make a custom error for overlap with negative implsNiko Matsakis-47/+43
2020-03-26permit negative impls for non-auto traitsNiko Matsakis-7/+253
2020-03-23Rollup merge of #69942 - estebank:sized-verbose-sugg, r=matthewjasperMazdak Farrokhzad-8/+8
Increase verbosity when suggesting subtle code changes Do not suggest changes that are actually quite small inline, to minimize the likelihood of confusion. Fix #69243.
2020-03-23Rollup merge of #70227 - LeSeulArtichaut:typo-def, r=CentrilMazdak Farrokhzad-6/+5
Only display definition when suggesting a typo Closes #70206 r? @Centril
2020-03-22Use more targetted span for error labelEsteban Küber-4/+4
2020-03-22Normalize wording of privacy access labelsEsteban Küber-6/+6
2020-03-21Add explanation message for E0224Nixon Enraght-Moony-2/+6
2020-03-21Bless testsLeSeulArtichaut-6/+5
2020-03-12update testsMark Mansi-5/+5
2020-03-10review commentsEsteban Küber-6/+1
2020-03-06Suggest removal of auto trait super traits and type paramsEsteban Küber-0/+5
2020-03-06Further tweak spans in ast validation errorsEsteban Küber-2/+4
2020-03-05review commentsEsteban Küber-2/+2
2020-03-04Tweak output for invalid negative impl AST errorsEsteban Küber-7/+3
2020-02-28keep predicate order and tweak outputEsteban Küber-9/+15
2020-02-28Tweak wordingEsteban Küber-3/+3
2020-02-28Mention the full path of the implementing traitEsteban Küber-3/+3
2020-02-28On single local candidate, use span labelEsteban Küber-6/+9
2020-02-22Add note regarding argument orderingvarkor-0/+2
2020-02-22Move generic arg / param validation to `create_substs_for_generic_args`varkor-8/+9
2020-02-17Do not emit note suggesting to implement trait to foreign typeLeSeulArtichaut-2/+0
Update tests Extend to other operations Refractor check in a separate function Fix more tests
2020-02-13Constness -> enum Const { Yes(Span), No }Mazdak Farrokhzad-1/+5
Same idea for `Unsafety` & use new span for better diagnostics.
2020-02-09Improve reporting errors and suggestions for trait boundsPatryk Wychowaniec-14/+38
2020-02-04Auto merge of #68544 - Aaron1011:remove-overlapping-traits, r=estebankbors-30/+13
Remove the `overlapping_marker_traits` feature See #29864 This has been replaced by `#[feature(marker_trait_attr)]` A few notes: * Due to PR #68057 not yet being in the bootstrap compiler, it's necessary to continue using `#![feature(overlapping_marker_traits)]` under `#[cfg(bootstrap)]` to work around type inference issues. * I've updated tests that used `overlapping_marker_traits` to now use `marker_trait_attr` where applicable The test `src/test/ui/overlap-marker-trait.rs` doesn't make any sense now that `overlapping_marker_traits`, so I removed it. The test `src/test/ui/traits/overlap-permitted-for-marker-traits-neg.rs` now fails, since it's no longer possible to have multiple overlapping negative impls of `Send`. I believe that this is the behavior we want (assuming that `Send` is not going to become a `#[marker]` trait, so I renamed the test to `overlap-permitted-for-marker-traits-neg`
2020-02-04Remove the `overlapping_marker_traits` featureAaron Hill-30/+13
See #29864 This has been replaced by `#[feature(marker_trait_attr)]` A few notes: * Due to PR #68057 not yet being in the bootstrap compiler, it's necessary to continue using `#![feature(overlapping_marker_traits)]` under `#[cfg(bootstrap)]` to work around type inference issues. * I've updated tests that used `overlapping_marker_traits` to now use `marker_trait_attr` where applicable The test `src/test/ui/overlap-marker-trait.rs` doesn't make any sense now that `overlapping_marker_traits`, so I removed it. The test `src/test/ui/traits/overlap-permitted-for-marker-traits-neg.rs` now fails, since it's no longer possible to have multiple overlapping negative impls of `Send`. I believe that this is the behavior we want (assuming that `Send` is not going to become a `#[marker]` trait, so I renamed the test to `overlap-permitted-for-marker-traits-neg`
2020-02-03Change wording for object unsafe because of assoc constEsteban Küber-3/+3
2020-02-02Deal with spans showing `std` libEsteban Küber-2/+7
Address #53081
2020-02-02Point at reason in object unsafe trait with `Self` in supertraits or ↵Esteban Küber-1/+4
`where`-clause
2020-02-02Account for `?Sized` type parameter boundsEsteban Küber-2/+2
2020-02-02Use more appropriate spans on object unsafe traits and provide structured ↵Esteban Küber-8/+14
suggestions when possible
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-10 20:32:13 +0000