Re: Re: RFC: Nested Classes
| From: | Tim Düsterhus | Date: | Thu, 08 May 2025 14:20:00 +0000 |
| Subject: | Re: Re: RFC: Nested Classes | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-127320@lists.php.net to get a copy of this message | ||
Hi
Am 2025-05-07 19:15, schrieb Rowan Tommins [IMSoP]:
There are three "platform dependency" pseudo-packages available for packages to depend on different aspects of Composer's version: https://getcomposer.org/doc/articles/composer-platform-dependencies.md If these didn't seem suitable, they could add another, like "composer-autoloader".Thank you, I stand corrected.
composer-runtime-api appears appropriate based on the description.
I think "autoloading tools and conventions would need to adapt" is definitely a cost to be weighed against the benefit, but not a blocker in itself.Yes, even with the support for these pseudo-packages, every author would need to remember to add those dependencies, which definitely has a cost on the entire ecosystem. Best regards Tim Düsterhus