Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[VarExporter] Add support for exporting named closures#61657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM, but I have a question about naming.
Is it something we could leverage for dumping object-bound closures in the DIC? Like#61656. But we don't serialize objects in DI arguments anyway, so it's probably a bad idea.
Uh oh!
There was an error while loading.Please reload this page.
I wouldn't add that to general DI values yet. The closure() function will allow it anyway, properly. |
c5ceb23 to23e1613CompareThank you@nicolas-grekas. |
a9dcea4 intosymfony:7.4Uh oh!
There was an error while loading.Please reload this page.
With first-class callables now allowed in attributes since PHP 8.5, it might become more common to find named closures in exported objects.