Add `HWND.INVALID_HANDLE_VALUE` into emitted output.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 124
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
After adding INVALID_HANDLE_VALUE, I found it under HANDLE when I needed it for a HWND parameter (WinVerifyTrust()). This required me to stand up my own value.
Describe the solution you'd like
When defining INVALID_HANDLE_VALUE, if HWND is emitted, emit a static readonly HWND INVALID_HANDLE_VALUE value.
Describe alternatives you've considered
Rolling my own as I'm doing already.
Additional context
https://learn.microsoft.com/en-us/windows/win32/api/wintrust/nf-wintrust-winverifytrust#parameters
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 locating the generator entry point that handles INVALID_HANDLE_VALUE and emits HWND-related output. Compare the existing HANDLE value with the requested HWND representation, using the WinVerifyTrust parameter context to confirm the intended type. Done means generated output includes a static readonly HWND INVALID_HANDLE_VALUE when HWND is emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100