about summary refs log tree commit diff
path: root/src/test/ui/trivial-bounds
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-885/+0
2022-12-28Use verbose suggestions for mutability errorsEsteban Küber-4/+10
2022-06-16diagnostics: fix trailing spaceklensy-1/+1
2022-05-12Add tests.Camille GILLOT-0/+163
2021-11-20Do not mention associated items when they introduce an obligationEsteban Kuber-6/+0
2021-10-03Practice diagnostic message conventionHirochika Matsumoto-36/+36
2021-09-16Point at call span that introduced obligation for the argEsteban Kuber-2/+6
2021-09-13Auto merge of #87915 - estebank:fancy-spans, r=oli-obkbors-1/+1
Use smaller spans for some structured suggestions Use more accurate suggestion spans for * argument parse error * fully qualified path * missing code block type * numeric casts
2021-08-16Use note to point at bound introducing requirementEsteban Küber-2/+5
2021-08-12Use smaller spans for some structured suggestionsEsteban Kuber-1/+1
Use more accurate suggestion spans for * argument parse error * fully qualified path * missing code block type * numeric casts * E0212
2021-08-11Modify structured suggestion outputEsteban Küber-3/+4
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-07-19Various diagnostics clean ups/tweaksEsteban Küber-3/+6
* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2020-09-29Say "doesn't" instead of "wouldn't" in convert messageCamelid-1/+1
2020-09-29Add article after "to"Camelid-1/+1
Also added missing backtick in "you can cast" message.
2020-09-02pretty: trim paths of unique symbolsDan Aloni-18/+18
If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-07-14Remove `Sized` `on_unimplemented` noteEsteban Küber-1/+0
2020-04-11rustc: Add a warning count upon completionRoccoDev-0/+10
2020-04-08Small tweaks to required bound spanEsteban 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-01-31Auto merge of #68080 - varkor:declared-here, r=petrochenkovbors-1/+1
Address inconsistency in using "is" with "declared here" "is" was generally used for NLL diagnostics, but not other diagnostics. Using "is" makes the diagnostics sound more natural and readable, so it seems sensible to commit to them throughout. r? @Centril
2020-01-25Don't use spaces before type ascription like colonsOliver Scherer-3/+3
2020-01-24Normalise notes with the/isvarkor-1/+1
2020-01-13Add "--emit=link"Aaron Hill-1/+1
This avoids a strange linker error that we get with only "--emit=mir" and "check-pass"
2020-01-13Convert test to check-passAaron Hill-4/+2
2020-01-13Don't run const propagation on items with inconsistent boundsAaron Hill-0/+6
Using `#![feature(trivial_bounds)]`, it's possible to write functions with unsatisfiable 'where' clauses, making them uncallable. However, the user can act as if these 'where' clauses are true inside the body of the function, leading to code that would normally be impossible to write. Since const propgation can run even without any user-written calls to a function, we need to explcitly check for these uncallable functions.
2019-11-18Surround types with backticks in type errorsEsteban Küber-1/+1
2019-11-10Make error and warning annotations mandatory in UI testsTomasz Miąsko-35/+47
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-10-28Use structured suggestion for unnecessary bounds in type aliasesEsteban Küber-1/+4
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+1
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-09-22On obligation errors point at the unfulfilled binding when possibleEsteban Küber-1/+1
2019-09-19When possible point at argument causing item obligation failureEsteban Küber-4/+4
2019-09-08Give method not found a primary span labelEsteban Küber-1/+1
2019-08-31Use span label instead of note for cause in E0631Esteban Küber-11/+5
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-6/+6
https://github.com/rust-lang/rust/issues/60532
2019-06-03Update tests for changes to cannot move errorsMatthew Jasper-2/+2
2019-05-29Update ui test suite to use dynmemoryruins-10/+10
2019-05-03Reword casting messageEsteban Küber-1/+1
2019-04-29Suggest try_into when possibleEsteban Küber-0/+4
2019-04-22Remove double trailing newlinesvarkor-1/+0
2019-04-22update tests for migrate mode by defaultMatthew Jasper-26/+7
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-1/+1
2019-03-11Update NLL testsVadim Petrochenkov-2/+2
2019-03-11Update testsVadim Petrochenkov-13/+13
2019-01-01Fix broken links to second edition TRPL.Corey Farwell-1/+1
Fixes https://github.com/rust-lang/rust/issues/57104.
2018-12-25Remove licensesMark Rousskov-170/+50
2018-10-29Don't emit cannot move errors twice in migrate modeMatthew Jasper-20/+0
2018-10-17Update output for borrowck=migrate compare mode.David Wood-0/+20
This commit updates the test output for the updated NLL compare mode that uses `-Z borrowck=migrate` rather than `-Z borrowck=mir`. The previous commit changes `compiletest` and this commit only updates `.nll.stderr` files.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 02:33:49 +0000