summary refs log tree commit diff
path: root/tests/ui/lint/unused/unused-attr-duplicate.stderr
diff options
context:
space:
mode:
authorMatthias Krüger <476013+matthiaskrgr@users.noreply.github.com>2025-06-23 06:07:19 +0200
committerGitHub <noreply@github.com>2025-06-23 06:07:19 +0200
commitf63fdde7646668d57f7674e8b55cd3eb6c19c45f (patch)
treee7b824b75bbd9f30d5ee8e62afae20bae8756036 /tests/ui/lint/unused/unused-attr-duplicate.stderr
parent8387d61a6ec05faee58f7cfb9c10799285067934 (diff)
parentb433aba3df460424dc3a94c875c34c13b23d6041 (diff)
downloadrust-f63fdde7646668d57f7674e8b55cd3eb6c19c45f.tar.gz
rust-f63fdde7646668d57f7674e8b55cd3eb6c19c45f.zip
Rollup merge of #141597 - Oneirical:unquestionable-instruction, r=jieyouxu
Document subdirectories of UI tests with README files

Part of rust-lang/rust#133895 and the [2025 Google Summer of Code](https://blog.rust-lang.org/2025/05/08/gsoc-2025-selected-projects/) associated project.

When adding a new UI test, one is faced with hundreds of subdirectories in `tests/ui` reflecting various categories. Knowing where to put the new test is not trivial, as many of the categories have slightly misleading names. For example, `moves` does not only refer to the `move` keyword but to functions taking ownership in general, whereas `allocator` does not refer to allocation in general but rather to the very specific `allocator_api` and `global_allocator` features.

Many contributors will therefore place their test at the top level of ̀`tests/ui` where it will be mixed with hundreds of unrelated tests.

This PR is a tentative move towards more clearly defined tag/categories, with a SUMMARY.md file documenting the true purpose of each subdirectory, placed inside `tests/ui`.

r? ``@jieyouxu``
Diffstat (limited to 'tests/ui/lint/unused/unused-attr-duplicate.stderr')
0 files changed, 0 insertions, 0 deletions