Strengthen weak refs when sorting in-place
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 2.3k
- Forks
- 646
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 49
Description
In #16162 , We determined to revert f6107ca24b4cf22dcf7fd69d65612ad718c48fca in commit d8306453385a4991e40b4738982bf9617b6c1ccf because it was breaking MLEHMANN/AnyEvent-HTTP-2.23. The plan was to put the commit back into 5.30 but I think we're too late in that cycle and the current one to put it back in.
So my question: Do we want to action this in v5.33.1 or do we want to drop this all together? What notifications will need to be made to make this happen?
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 by reviewing issue #16162 and the referenced commits f6107ca24b4cf22dcf7fd69d65612ad718c48fca and d8306453385a4991e40b4738982bf9617b6c1ccf, including the MLEHMANN/AnyEvent-HTTP-2.23 regression. Determine whether the reverted change should be reconsidered for v5.33.1 and identify the release notifications required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100