Use C23 free_sized especially with short lived data (more so in tight loops), discussion for later
Open
Nobody has claimed this yet.
Feature
Status: Needs Triage
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.2k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
To see for the next major release (likely 9.0) and giving the time for the various libcs to actually implement it.
We bother giving an explicit size, the benefit doing so is performance. Indeed, the underlying memory allocator does not need to read the metadata to figure out the block size in that case.
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 locating PHP's current explicit-size deallocation sites and checking which target libcs support the C23 free_sized API. Compare its potential impact for short-lived allocations and tight loops, then define the compatibility and scope required for the likely 9.0 release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100