Profiling: Why we have exclude methods in #initialization protocol?
Open
Nobody has claimed this yet.
question
- Dominant language
- Smalltalk
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In the profiling, we mark methods in #initialization protocol as unsafe. why?
also in add input amplifier.
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
Begin at the profiling logic that marks methods in the #initialization protocol as unsafe, then inspect the corresponding add input amplifier path. Done means identifying and documenting why both exclusions are required, or confirming that either exclusion can be removed.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100