microsoft / microsoft/arcana.cpp
Make UWP capabilities header-only
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 87
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Because Arcana's UWP offerings aren't header-only
@syntheticmagus If memory serves, it shouldn't be too much work to make it header-only, which would also make it considerably more portable and easy to consume.
Originally posted by @ryantrem in https://github.com/microsoft/arcana.cpp/pull/2#issuecomment-520673074
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
No files or tests are named in the issue. Start by locating the UWP capabilities implementation and identifying which offerings currently require compiled sources; then determine how the existing build and consumption paths expose them. Done means the UWP capabilities are header-only and remain portable and easy to consume.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100