take this step. [3] This might also be relevant for the PHP Foundation and
Perforce. Maybe they can help assess the situation.
--
Kind regards,
Vincent de Lau
[1]:
https://lunduke.locals.com/post/6263331/sanctions-hit-linux-kernel-russian-programmers-banned
[2]: https://www.youtube.com/watch?v=L5Ec5jrpLVk
[3]: https://www.phoronix.com/news/Linus-Torvalds-Russian-Devs
gation and discussion. My only hope now is
that the people voting take this into consideration, especially as this is now
being rushed into 8.4.
--
Vincent de Lau
me topics
this leads to competing interpretations, sometimes they lead to de-facto
standards. In the end, nothing and nobody is perfect. PHP, internals, the FIG,
the PSRs, all are made by, or consist of, people trying their best.
--
Vincent de Lau
[1]: https://getcomposer.org/doc/04-schema.md#autoload
I immediately
had to think about the rejected 'Coercive Types for Function Arguments' RFC
Zeev created as an alternative to the 'Scalar Type Declaration' RFC which was
ultimately chosen and implemented.
https://wiki.php.net/rfc/coercive_sth
It seems that parts of what that RFC sugge
ted than the RFC technically defines them to be.
Furthermore, I see a lot of reasoning in favour of the prefix syntax in
relation to limitations of other language constructs like property promotion.
While I don't think it is fair to expect this RFC should fix those, to me it
feels we are compounding 'errors'.
Thanks to both you and Ilija for all the hard work on these RFC's, it is much
appreciated!
--
Vincent de Lau
