Add memory_resource diagnostics interface
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- performance
Research direction
Start by reviewing the issue's proposed diagnostics interface and the existing non-rtti pmr::memory_resource boundary. Determine how generic code should detect support with rtti and obtain diagnostics; done requires resolving the non-rtti-to-interface conversion design and defining the common interface.
Written by the indexing model from the issue text.
Description
It's common for applications to maintain metrics for custom memory_resources. We should define a common interface that uses rtti allowing generic code to see if a given resource supports diagnostics and to obtain them.
Difficulties here include how to go from non-rtti pmr::memory_resource to the diagnostics interface type.
- Dominant language
- C++
- Stars
- 18
- Forks
- 4
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from OpenCyphal/CETL
-
accepted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenCyphal/CETL#271 ·
-
accepted
Difficulty 3/5 1-2 days Newbie friendliness 70/100
OpenCyphal/CETL#270 ·
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 45/100
OpenCyphal/CETL#262 ·
-
under consideration
Difficulty 4/5 3-5 days Newbie friendliness 35/100
OpenCyphal/CETL#252 ·
-
tracking
Difficulty 3/5 1-2 days Newbie friendliness 35/100
OpenCyphal/CETL#194 ·
Similar issues
-
good first issue hardware-report help wanted
Difficulty 1/5 Under an hour Newbie friendliness 66/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
launcher: settings are never saved on macOS — QSettings SystemScope points to /Library/PreferencesOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
documentation ready
Difficulty 1/5 Under an hour Newbie friendliness 80/100
MartinPTielemans/ilo#3806 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100