Add memory_resource diagnostics interface

Open
#176 1 comment 0 reactions 0 assignees View on GitHub

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

under consideration

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenCyphal/CETL

All issues in OpenCyphal/CETL

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.