rust-windowing / rust-windowing/softbuffer
Reduce the complexity of the Win32 implementation
Open
Nobody has claimed this yet.
DS - Win32
help wanted
- Dominant language
- Rust
- Stars
- 506
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
There's no reason the Win32 backend should be starting its own threads in a sane application.
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 Win32 backend and the code that starts its threads. Determine how the backend can operate without starting its own threads; done means the Win32 implementation no longer creates them while retaining its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100