Friendly overloads should translate `out PCWSTR` to `out string`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 124
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
In process of doing this, keep @kennykerr's advice in mind:
If there's no attribute that says how to free the PWSTR then you let the API free it and you simply copy the string. IXmlReader is an example of this. If there's an attribute that indicates how to free the memory then you use that allocator. ISpellingError is an example of this.
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 friendly overload generation for Win32 methods that expose out PCWSTR values. Use the IXmlReader and ISpellingError examples from the issue to understand when strings are copied or freed with an indicated allocator; done means the generated overload exposes out string with the correct memory-management behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100