OpenAssetIO / OpenAssetIO/OpenAssetIO-TraitGen
Add `static` accessor/mutator conveniences
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
What
Generate static conveniences for trait accessors/mutators, such that the (C++) refcount of the TraitsData is not modified.
Why
C++ purists will balk at wrapping a TraitsData in a short-lived trait view to operate on it, likely necessitating a shared_ptr copy and refcount bump. This is a potentially measurable performance hit in large-volume operations.
E.g. we can add static variants such as getLocationFrom(const TraitsData&), and similarly setLocationTo.
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
The issue does not name any source files, tests, or generator entry points. Start by locating where trait accessors and mutators are generated, then determine how static variants should be represented and verified without changing TraitsData reference counts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100