microsoft / microsoft/win32metadata
Inconsistent error disposition around named pipe functions UNICODE v ANSI
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 149
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 4
Description
It seems like `CreateNamedPipeA` is tagged as a `--with-setlasterror` function while `CreateNamedPipeW` is not. It seems like these should have the same error bucketing (they should both be functions that call `SetLastError` looking at the namedpipeapi docs on learn).
Similarly `CallNamedPipeW`, `GetNamedPipeClientComputerNameW`, `GetNamedPipeHandleStateW`, and `WaitNamedPipeW` all also should be get `--with-setlasterror` functions just like their ANSI counter parts.
Contributor guide
Research direction
Locate the metadata entries for CreateNamedPipeA/W, CallNamedPipeW, GetNamedPipeClientComputerNameW, GetNamedPipeHandleStateW, and WaitNamedPipeW, then compare their --with-setlasterror annotations with the ANSI counterparts. Check the namedpipeapi documentation cited in the issue and verify that the generated metadata gives matching error disposition for each ANSI/Unicode pair.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100