On 15 Jul 2014, at 20:43, Andrey Andreev <n...@devilix.net> wrote: > I'm sorry, I know what you mean here and I'm not criticizing you > specifically (in fact, I'm intentionally taking it ouf of context), > but that's "PHP internals", not "PHP community". > > The PHP community that I know, wants to have _both_ type cast hinting > and strict type declarations.
I’m not sure that’s quite the case. There are camps wanting one, there are camps wanting the other, I suppose some want both, but to me that seems like a not-a-compromise compromise solution. The point of this RFC, to some extent, is to be a reasonable compromise between completely strict declarations and cast hinting, providing the safety of the first and the flexibility of the second. I think it strikes the balance well. It’s also that I, myself, actually would prefer this proposal to either cast hinting or strict declarations… so that’s three ways to support if we’re going down that route. Really, I think we should settle on a compromise, not on one way, the other, or both. This RFC is a compromise. -- Andrea Faulds http://ajf.me/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
