Document mutation of objects within a message
Open
Nobody has claimed this yet.
documentation
- Dominant language
- C++
- Stars
- 693
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
- Adding mixins is always safe
- Removing self is equivalent to
delete this(safe as long as it's the last thing in the method) - Removing mixins other than self in an unicast is safe
- Removing mixins in a multicast is TBD
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 names no file, test, or entry point. First locate the documentation covering message and object mutation, then use the listed safe and TBD cases as the scope; done means those cases are documented without resolving the multicast question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100