HaxeFlixel / HaxeFlixel/flixel
Remove signal.destroy
Open
Nobody has claimed this yet.
- Dominant language
- Haxe
- Stars
- 2.2k
- Forks
- 522
- Avg merge
- 34m
- Merged PRs (30d)
- 1
Description
Why have a destroy when removeAll should clear all references and allow garbage collection, while still allowing the signal to be used in the future.
Tasks:
- Deprecate destroy
- Clear
pendingRemovein removeAll
Contributor guide
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 at the signal implementation and compare destroy with removeAll. Deprecate signal.destroy and ensure removeAll clears pendingRemove while leaving the signal reusable. No file or test is named in the issue, so locate the relevant signal code before changing it.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100