microsoft / microsoft/picologging
Cap vector size or decide on a better map type.
Open
Nobody has claimed this yet.
good first issue
help wanted
- Dominant language
- Python
- Stars
- 779
- Forks
- 29
- Avg merge
- 23h 3m
- Merged PRs (30d)
- 1
Description
* TODO : Cap vector size or decide on a better map type.
Contributor guide
No contributing guide indexed for this repository
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 in src/picologging/logrecord.cxx at line 15 and inspect the vector usage behind the TODO. Clarify whether the vector needs a bounded size or a different map type, then document the chosen approach and verify that the affected logging behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100