PHP C extension

[arshidkv12]

I have developed a PHP C extension that brings Laravel traits, such as Macroable and Singleton, into native performance. Please consider including it as a core extension requirement. https://packagist.org/packages/arshidkv12/traitify

[macropay-solutions]

Hi. Does it handle this case for singletons #56672 ?

[henzeb]

I doubt that they ever will make this a requirement. It's not exactly automatically replace the laravel traits. It's an optional choice you make by setting up the implementation you want. And even if it would replace all that is being used internally, it still wouldn't be part of the framework, because it would make it harder to install a fresh new project... As interesting this might seem for those that seek performance.

[henzeb]

But it's still an extra step.

[henzeb]

Not to mention one has to have pie installed first...

[arshidkv12]

Yes, correct :)

[Sophist-UK]

IMO there is nothing to stop an individual Laravel user from installing this and making their own code use it, however...

1. It is unclear what the real-life actual performance gains are - they would need to be pretty darned significant for me to even start to consider using this because of the potential risks of incompatibility that it might introduce. These need to be benchmarked and spelled out.

2. It is unclear whether installing the PHP extension creates any incompatibilities with existing code. However I suspect that by implementing methods using the same names as Laravel methods that this is highly likely. It also needs to be compatible with the entire Laravel ecosystem, not just with the Laravel core i.e. is it compatible with Octane?

3. It is unclear whether Laravel will treat a users Traitify\Singleton class exactly as it treats current singletons - but I think it pretty likely that it doesn't

4. Because it is not backwards compatible with existing code (i.e. it needs Traits) then I think it will be extremely unlikely that it will ever make it into Laravel itself.

I think that some explicit clarification around these points and changes to this package where needed and technically possible to improve the compatibility would most likely help.

You might want to consider changing it so that it uses different names from Laravel - and hopefully this will then avoid the need for using Traits. For users coding to use this explicitly it makes zero difference, but from a compatibility perspective it then enables you to have conditional code which checks whether the extension is installed and uses it if it is and doesn't use it if it isn't. If you can achieve this, and the performance gains are significant, then I can potentially see it being included in Laravel.

[shaedrich]

IMO there is nothing to stop an individual Laravel user from installing this and making their own code use it, however...

Some hosting providers might be less likely to offer new and fairly unknown extensions