about summary refs log tree commit diff
path: root/src/test/ui/issues/issue-17546.stderr
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-73/+0
2022-12-13Make some diagnostics not depend on the source of what they reference being ↵Oli Scherer-8/+4
available
2021-08-11Modify structured suggestion outputEsteban Küber-4/+4
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-08-04Remove trailing whitespace from error messagesFabian Wolff-2/+2
2020-07-27mv std libs to library/mark-2/+2
2020-06-09Remove noisy suggestion of hash_map #72642Ayush Kumar Mishra-6/+4
Fixed failing test-cases Remove noisy suggestion of hash_map #72642 Fixed failing test-cases
2020-05-07reword "possible candidate" import suggestionAndy Russell-2/+2
2020-05-05Ignore SGX on a few ui testsMohsen Zohrevandi-4/+4
2020-04-02tests: remove ignore directives from tests that mention core/alloc/std spans.Eduard-Mihai Burtescu-4/+4
2020-01-10Ignore platforms that can't point to stdEsteban Küber-4/+4
2020-01-10Use `def_span` to minimize definition span to first line when possibleEsteban Küber-20/+8
2020-01-10Point at the span for the definition of crate foreign ADTsEsteban Küber-4/+26
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+4
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-19Fix plural mistake in emitter.rsvarkor-2/+2
2019-10-16update ui testsGuillaume Gomez-0/+1
2019-10-13Bring attention to suggestions when the only difference is capitalizationEsteban Küber-2/+2
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-1/+0
2019-01-09clarify resolve typo suggestionAndy Russell-8/+18
Include the kind of the binding that we're suggesting, and use a structured suggestion.
2018-12-25Remove licensesMark Rousskov-4/+4
2018-12-22enum type instead of variant suggestion unificationZack M. Davis-2/+2
Weirdly, we were deciding between a help note and a structured suggestion based on whether the import candidate span was a dummy—but we weren't using that span in any case! The dummy-ness of the span (which appears to be a matter of this-crate vs. other-crate definition) isn't the right criterion by which we should decide whether it's germane to mention that "there is an enum variant"; instead, let's use the someness of `def` (which is used as the `has_unexpected_resolution` argument to `error_code`). Since `import_candidate_to_paths` has no other callers, we are free to stop returning the span and rename the function. By using `span_suggestions_`, we leverage the max-suggestions output limit already built in to the emitter, thus resolving #56028. In the matter of message wording, "you can" is redundant (and perhaps too informal); prefer the imperative.
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+55