wil::reg should expose an object type to unique_hkey and shared_hkey
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3k
- Forks
- 300
- Avg merge
- 19h 12m
- Merged PRs (30d)
- 1
Description
Feature request: expose a type for wil::unique_hkey and wil::shared_hkey so that the RAII objects that manage the HKEY resource also get methods for acting on that HKEY.
e.g.
wil::unique_hkey key = wil::reg::open_unique_key(HKLM, L"My\Registry\Path");
DWORD value = key.get_value_dword(L"value_name");
vs. today it's all free functions.
wil::unique_hkey key = wil::reg::open_unique_key(HKLM, L"My\Registry\Path");
DWORD value = wil::reg::get_value_dword(key.get(), L"value_name");
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 wil::unique_hkey, wil::shared_hkey, wil::reg::open_unique_key, and the existing wil::reg free functions. Compare the requested object methods with the current free-function behavior; done means both RAII HKEY types expose equivalent registry operations without requiring key.get().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100