rust-lang / rust-lang/rust-playground
Separate stderr and compiler output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
Program stderr kind of gets blended in with the compiler output:
The output "middle" is easy to miss since there's no visual separation from the compiler message. It would be nice to have a separate section "Compiler Output" to go with the existing "Standard Error" and "Standard Output" sections.
Making the output sections collapsible under the heading might be good as well, if having an extra separator would consume too much extra vertical space.
(snippet for example:)
fn main() {
let x = 10u32; // trigger unused
println!("start");
eprintln!("middle");
println!("end");
}
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the Playground UI code that renders the existing Standard Error and Standard Output sections, then reproduce the Rust snippet from the issue to observe how compiler output and stderr are currently combined. Done means compiler output is visibly separated from Standard Error and Standard Output; collapsible sections remain an optional design choice to resolve.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100