llnl / llnl/camp

Type erased resource and event implementation

Open
#144 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
107
Forks
26
Avg merge
8d 11h
Merged PRs (30d)
2

Description

My understanding is that these are supposed to be fairly light weight classes. I think resources are trivial most of the time, but events may need to own their data.
The type erasure is currently implemented with inheritance and shared_ptr. Does it make sense to use std::variant when we move to c++17?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the resource and event classes and their current type-erasure implementation using inheritance and shared_ptr. Compare their ownership needs with a possible std::variant design for C++17; done requires an agreed design and corresponding implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
compilers
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.