Allow object construction from `object_mutation` and `mutate`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 693
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Currently an object can be constructed from a type, but only if the type is composed of default-constructible mixins. If not, one must construct an empty object and immediately mutate, which will call several functions to get the domain and empty type to be immediately replaced by the one from the mutation.
It would be useful to allow providing mixin constructors to an object construction. To maintain type safety, this will involve creating several very similar types for mutations: ones which have no object, and ones that do (the latter being the current ones).
Besides the perf reasons, having this option would allow for more concise and readable code.
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
Start by locating the object construction, object_mutation, and mutate APIs described in the issue, then trace the existing type definitions for mutations that carry an object. Compare how constructors and type safety are handled today. Done means construction can accept mixin constructors without the empty-object replacement path while preserving the required type distinctions; no files or tests are named in the issue.
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
- 30/100