Optimize cxplat_winuser/rundown_winuser.cpp
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105
- Forks
- 34
- Avg merge
- 3d 39m
- Merged PRs (30d)
- 5
Description
In PR #94, Nick writes:
Whis is this so complicated, and not simply a ref count and a completion event? Is it purely for debugging reasons? If so, we need a hyper optimized release mode version.
Dave writes:
we should move any workarounds for "no free API in kernel mode" over to the usersim directory and keep the complexity out of the cxplat directory.
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
Start by reading cxplat_winuser/rundown_winuser.cpp and the discussion in PR #94. Compare the complexity in cxplat with the proposed placement of kernel-mode workarounds in usersim, then establish the intended optimized release behavior. Done should mean the workaround complexity is appropriately separated and the rundown implementation is measurably simpler or faster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100