Free mixin features
Open
Nobody has claimed this yet.
question
- Dominant language
- C++
- Stars
- 693
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Is it a good idea to allow free mixin features. This would be an additional list of features when creating a type, which is not carried in by one of the participating mixins.
- On one hand, zero-sized mixins can do the same job
- However with free features the object buffer becomes smaller and we don't have to manage it
I'm so far leaning against this, but leaving it here for posterity
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
No files, tests, or entry points are named. Start by reviewing how types and participating mixins are created, then compare the proposed free-feature list with zero-sized mixins and object-buffer management. The issue is not implementation-ready; a concrete decision and scope would be needed before there is a verifiable done state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100