rust-windowing / rust-windowing/winit
Logging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Having proper logging would make things easier for everyone, and I assume most people would agree with that. Telling someone to rerun with WINIT_LOG_LEVEL=debug is much better than saying "rebuild against this branch I made that has some println added that are hopefully relevant", which is something I've had to do a few times now.
Is slog the best way to go about adding logging? I'm also in favor of making the sink global, since passing it around would make this much more tedious to implement.
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 does not name any files or tests. Start by locating the existing println-based debugging mentioned in the report, then review the proposed slog integration and global sink design. Done would require an agreed logging design and implementation across the relevant code paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100