about summary refs log tree commit diff
path: root/tests/ui/pub
AgeCommit message (Collapse)AuthorLines
2025-08-19bless tests with new lint messagesKarol Zwolak-2/+2
2025-06-03Use non-2015 edition paths in tests that do not test for their resolutionLukas Wirth-13/+13
This allows for testing these tests on editions other than 2015
2025-05-03Correct warning message in restricted visibilityyuk1ty-0/+52
2025-04-08UI tests: add missing diagnostic kinds where possibleVadim Petrochenkov-5/+5
2025-02-14Trim suggestion parts to the subset that is purely additiveMichael Goulet-6/+6
2025-02-14Consider add-prefix replacements tooMichael Goulet-15/+10
2025-02-14Use underline suggestions for purely 'additive' replacementsMichael Goulet-3/+2
2025-02-10Show diff suggestion format on verbose replacementEsteban Küber-12/+18
``` error[E0610]: `{integer}` is a primitive type and therefore doesn't have fields --> $DIR/attempted-access-non-fatal.rs:7:15 | LL | let _ = 2.l; | ^ | help: if intended to be a floating point literal, consider adding a `0` after the period and a `f64` suffix | LL - let _ = 2.l; LL + let _ = 2.0f64; | ```
2024-08-03Bless test falloutMichael Goulet-2/+2
2024-08-03Revert "Rollup merge of #125572 - mu001999-contrib:dead/enhance, r=pnkfelix"Michael Goulet-8/+6
This reverts commit 13314df21b0bb0cdd02c6760581d1b9f1052fa7e, reversing changes made to 6e534c73c35f569492ed5fb5f349075d58ed8b7e.
2024-07-18Rollup merge of #127656 - RalfJung:pub_use_of_private_extern_crate, ↵Matthias Krüger-1/+16
r=petrochenkov make pub_use_of_private_extern_crate show up in cargo's future breakage reports This has been a lint for many years. However, turns out that outright removing it right now would lead to [tons of crater regressions](https://github.com/rust-lang/rust/pull/127656#issuecomment-2233288534) due to crates depending on an ancient version of `bitflags`. So for now this PR just makes this future-compat lint show up in cargo's reports, so people are warned when they use a dependency that is affected by this. r? `@petrochenkov`
2024-07-18make pub_use_of_private_extern_crate show up in future breakage reportsRalf Jung-1/+16
2024-07-12Make parse error suggestions verbose and fix spansEsteban Küber-5/+25
Go over all structured parser suggestions and make them verbose style. When suggesting to add or remove delimiters, turn them into multiple suggestion parts.
2024-07-08Add suggestions for possible missing `fn`, `struct`, or `enum` keywordstrevyn-59/+46
2024-06-11Rollup merge of #125913 - fmease:early-lints-spruce-up-some-diags, r=Nadrieril许杰友 Jieyou Xu (Joe)-2/+6
Spruce up the diagnostics of some early lints Implement the various "*(note to myself) in a follow-up PR we should turn parts of this message into a subdiagnostic (help msg or even struct sugg)*" drive-by comments I left in #124417 during my review. For context, before #124417, only a few early lints touched/decorated/customized their diagnostic because the former API made it a bit awkward. Likely because of that, things that should've been subdiagnostics were just crammed into the primary message. This PR rectifies this.
2024-06-05Detect pub structs never constructed and unused associated constants in traitsr0cky-5/+7
2024-06-03Spruce up the diagnostics of some early lintsLeón Orell Valerian Liehr-2/+6
2024-05-22Cleanup: Fix up some diagnosticsLeón Orell Valerian Liehr-2/+3
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-11/+11
2024-01-02Adjust compiler tests for unused_tuple_struct_fields -> dead_codeJake Goulding-4/+4
2023-11-24Show number in error message even for one errorNilstrieb-13/+13
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-09-06Add explanatory note to 'expected item' errorGurinder Singh-0/+2
2023-08-02Replace old private-in-public diagnostic with type privacy lintsBryanskiy-65/+13
2023-06-29Fix type privacy lints error messageBryanskiy-13/+13
2023-06-15privacy: Feature gate new type privacy lintsVadim Petrochenkov-10/+11
2023-06-12Private-in-public lints implementationBryanskiy-4/+60
2023-02-01tests: rename test cases to match new behaviourXiretza-2/+2
2023-02-01Fix condition for "missing `struct`" diagnostic on tuple structsXiretza-6/+41
The check previously matched this, and suggested adding a missing `struct`: pub Foo(...): It was probably intended to match this instead (semicolon instead of colon): pub Foo(...);
2023-01-11Move /src/test to /testsAlbert Larsan-0/+464