Hi! > I don't know what is complicated about "string|Stringable" or "Foo|Bar" > since it is super self-explanatory. However, I find myself checking the
It may be self-explanatory for you. It's much less self-explanatory for somebody just starting to learn. It is also very dangerous - if it's either Foo or Bar, can you call Foo::stuff on it or not? If it's string or not string, can you call strlen on it? Etc., etc. It adds a lot of cognitive load and complicates the whole picture. You may have a specific use case where it is useful (which we have yet to see btw) but please remember it's a language with literally millions of use cases and users. > docs (IDE or online) in which order I need to pass arguments to one of > the various mixed up functions in the core all the time. Which takes about 0.5 seconds. Can we please not waste time on discussing argument order some 9000th time? > PHP is not easy, it has so many quirks that one needs to know of that > you could make a PhD only for that. PHP has some quirks, but it doesn't take PhD to look up argument order in a manual. Anyway, having super-complicated type algebra does not help any with argument order, so I'm not sure why it's brought here at all. > https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ > > This contains A LOT of that stuff. Oh, could we please stop referring to this list of nitpicks each time we discuss the language? About 90% of it is not worth the bytes spent on it for discussing it again and again. Using it as some kind of magic "some guy wrote article bashing PHP, therefore my proposals need to be accepted" card makes no sense at all. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
