about summary refs log tree commit diff
path: root/src/test/ui/associated-const
AgeCommit message (Collapse)AuthorLines
2020-10-15Migrate from `associated-const` to `associated-consts`Yuki Okushi-863/+0
2020-09-26Make invalid integer operation messages consistentvarkor-25/+25
2020-09-19Address review commentsOliver Scherer-7/+7
2020-08-19Fix bad printing of const-eval queriesThibsG-1/+1
2020-06-26Show the values and computation that would overflow a const evaluation or ↵Oliver Scherer-19/+19
propagation
2020-05-02Point at associated types when they have a default typeEsteban Küber-2/+0
Associated types with a default type in a trait can't be relied upon to remain of that default type when in use, so literals of that type can't be used in the trait's items. Point at the associated type and state that information. Reduce verbosity for associated consts of the wrong type.
2020-05-02When a projection is expected, suggest constraining or calling methodEsteban Küber-1/+1
2020-04-24Remove redundant `descr`/`descriptive_variant` methods from HIR.Eduard-Mihai Burtescu-2/+2
2020-04-14typeck: always expose repeat count `AnonConst`s' parent in `generics_of`.Eduard-Mihai Burtescu-11/+4
2020-04-05"cannot resolve" → "cannot satisfy"Esteban Küber-2/+2
2020-04-03Add comment explaining the reversed operands testsjumbatm-59/+60
Also, fix the goofy reversed names with something clearer.
2020-04-02Move #69020 test to ui/associated-const + rebless.jumbatm-0/+209
2020-03-29Tweak `suggest_constraining_type_param`Esteban Küber-8/+6
Some of the bound restriction structured suggestions were incorrect while others had subpar output.
2020-03-25Rollup merge of #70319 - lcnr:issue63695, r=eddybDylan DPC-11/+23
correctly normalize constants closes #70317 implements https://github.com/rust-lang/rust/issues/70125#issuecomment-602133708 r? eddyb cc @varkor
2020-03-24improve normalize cycle errorBastian Kauschke-11/+23
2020-03-22Use more targetted span for error labelEsteban Küber-4/+4
2020-03-22Normalize wording of privacy access labelsEsteban Küber-1/+1
2020-02-28keep predicate order and tweak outputEsteban Küber-3/+5
2020-02-28Tweak wordingEsteban Küber-1/+1
2020-02-28Mention the full path of the implementing traitEsteban Küber-1/+1
2020-02-28On single local candidate, use span labelEsteban Küber-2/+3
2020-02-21Fix rebase damageJonas Schievink-2/+11
2020-02-21Fix tests that fail with `--emit metadata`Jonas Schievink-5/+15
2020-02-21Add regression tests for issuesJonas Schievink-1/+2
2020-02-21Fix tests after rebaseJonas Schievink-2/+2
2020-02-21Add tests for assoc. const defaultsJonas Schievink-0/+182
2020-02-09Improve reporting errors and suggestions for trait boundsPatryk Wychowaniec-4/+12
2020-02-03Change wording for object unsafe because of assoc constEsteban Küber-1/+1
2020-02-02Wording changes to object unsafe trait errorsEsteban Küber-1/+5
Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-01-24Normalise notes with the/isvarkor-1/+1
2020-01-11Rollup merge of #68014 - estebank:unify-e0599, r=cramertjYuki Okushi-1/+1
Unify output of "variant not found" errors Fix #49566.
2020-01-08Explain that associated types and consts can't be accessed directly on the ↵Esteban Küber-2/+10
trait's path
2020-01-08Unify output of "variant not found" errorsEsteban Küber-1/+1
2019-12-20Rollup merge of #67127 - estebank:disambiguate-suggestion, r=varkorMazdak Farrokhzad-2/+8
Use structured suggestion for disambiguating method calls Fix #65635.
2019-12-11Use structured suggestion for disambiguating method callsEsteban Küber-2/+8
Fix #65635.
2019-12-10Deduplicate logicEsteban Küber-6/+10
2019-11-18Surround types with backticks in type errorsEsteban Küber-2/+2
2019-11-18Remove E0308 note when primary label has all infoEsteban Küber-1/+1
2019-11-18Specific labels when referring to "expected" and "found" typesEsteban Küber-4/+4
2019-10-22Add test for issue-63496Yuki Okushi-0/+30
2019-10-15Use structured suggestion for restricting boundsEsteban Küber-4/+4
When a trait bound is not met and restricting a type parameter would make the restriction hold, use a structured suggestion pointing at an appropriate place (type param in param list or `where` clause). Account for opaque parameters where instead of suggesting extending the `where` clause, we suggest appending the new restriction: `fn foo(impl Trait + UnmetTrait)`.
2019-10-11Print lifetimes with backticksYuki Okushi-1/+1
2019-09-18Add explanation to type mismatch involving type params and assoc typesEsteban Küber-0/+2
2019-09-02On object safety violation, point at source when possibleEsteban Küber-2/+3
2019-08-31Use span label instead of note for cause in E0631Esteban Küber-16/+9
2019-07-24Adjust tests for method disambiguation helpIlija Tovilo-0/+2
2019-07-03Migrate compile-pass annotations to build-passYuki Okushi-1/+1
2019-05-29Update ui test suite to use dynmemoryruins-3/+3
2019-03-23Tweak spans for E0599Esteban Küber-3/+1
2019-03-13Rollup merge of #59083 - kyren:master, r=varkorMazdak Farrokhzad-6/+31
Fix #54822 and associated faulty tests Type checking associated constants can require trait bounds, but an empty parameter environment was provided to the trait solver. Providing an appropriate parameter environment seems to fix #54822 and also make one of the cases in src/test/ui/nll/trait-associated-constant.rs that should compile successfully do so. It also (slightly) improves the error message in src/test/ui/associated-const/associated-const-generic-obligations.rs
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-26 17:46:43 +0000