`forbid-output` is inconsisently named versus `error-pattern` and `normalize-stderr-test` and friends
Open
Nobody has claimed this yet.
A-compiletest
C-bug
E-needs-investigation
T-bootstrap
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Actually, I'll revisit
forbid-outputin a follow-up because the naming is strange and inconsistent versuserror-patternandnormalize-stderr-testand whatever...
Originally posted by @jieyouxu in https://github.com/rust-lang/rust/issues/134738#issuecomment-2561663717
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions forbid-output, error-pattern, and normalize-stderr-test, but names no files or tests. Start by locating these directives and comparing their naming conventions; done means an agreed, consistent name and the related references updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100