Engine calls to private destructors cause errors
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
While private magic method declarations result in a visibility warning, they still work when invoked by the engine as in the cases of __debugInfo (and __sleep since 8.1)
Private destructors however cause errors whenever an instance goes out of scope. The engine should always be able to invoke a destructor when destroying an instance.
PHP Version
8.4
Operating System
No response
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 reproducing the private-destructor failure with the linked 3v4l example and inspect the PHP engine's object-destruction path. The issue names no source file or regression test, so trace how destructor visibility is handled when an instance goes out of scope. Done means private destructors no longer cause errors during engine-driven destruction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100