SysFreeStringSafeHandle has no way of actually getting the held string value
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.
The SysFreeStringSafeHandle type provides no mechanism for actually accessing the string that it supposedly wraps.
Describe the solution you'd like
An override of the ToString() method, perhaps, or a new property or method for getting the string value.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
I'm using the QueryPathOfRegLib API, and the generated "higher level" wrapper function has an out parameter typed as a SysFreeStringSafeHandle. Also, the way that the function creates the handle and returns it as an out parameter prevents the caller from automatically freeing it with a using statement/expression.
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 with the SysFreeStringSafeHandle type and the generated higher-level QueryPathOfRegLib wrapper described in the issue. Determine how callers can access the held string and how the out parameter's lifetime is managed. Done means the API provides a usable string-access mechanism and the handle can be safely released by callers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100