You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in your most recent macro, you are using ~> as the symbol for short closures. I am interested in the reason behind this choice. Is it for technically reasons, as it may be difficult or impossible to just use => as symbol? Or could it be that you are anticipating that PHP will be using ~> for its own short closure implementation in future, so it is an attempt to be consistent with the language itself? Just curious.
The text was updated successfully, but these errors were encountered:
It's a combination of both. There was a lot of extra code to deal with edge-cases for =>, and one of the things I want to try and do with this library is ease folks into future PHP features (if the short-closures RFC ever lands).
I noticed that in your most recent macro, you are using ~> as the symbol for short closures. I am interested in the reason behind this choice. Is it for technically reasons, as it may be difficult or impossible to just use => as symbol? Or could it be that you are anticipating that PHP will be using ~> for its own short closure implementation in future, so it is an attempt to be consistent with the language itself? Just curious.
The text was updated successfully, but these errors were encountered: