> On 28 Oct 2017, at 20:23, Oscar Otero <oscarot...@gmail.com> wrote: > > > Ok, I see. > Could this be solved with php 7.2, that implements parameter type widening? > (https://wiki.php.net/rfc/parameter-no-type-variance) > So we can keep releasing interfaces compatible with php5 and in a short > future release the v2.0 compatible with php ^7.2. > I think that this feature was added specially for things like this. > >> El 28 oct 2017, a las 19:54, Michael Cullum <m...@michaelcullum.com> >> escribió: >> >> Oscar, >> >> This was discussed on Slack however those there agreed it didn't make sense >> to do releasing new version of the interface for each PHP version. >> >> The reason being as then you have a client application that has one library >> requiring one version, and another library requiring another version which >> would be incompatible with each other. >> >> Implementing libs also couldn't support both 1.x and 2.x if they support PHP >> 7 as you can't leave out the type declaration of extending an interface, and >> having it in PHP 5 will throw an error. So implementing libs would require >> 1.x or 2.x but never both causing the above issue in client applications.
I also brought this up, not because I am not aware that this can lead to messy situations but in order to give one less reason not to support return type hinting in new specs. Finishing a PSR and getting it into libs and then integrated into frameworks in a stable release takes long enough. Lets not end up in a situation where PSR compliance means being 1-2 PHP versions behind in terms of features. In this spirit I propose to always allow (maybe even mandate) using the latest PHP versions in PSRs. As well as encouraging updating existing PSRs (though maybe not necessarily for every PHP release with relevant new features ..). For the most part we are only affected by things that impact interfaces (ie. new type hinting, new classes etc), regards, Lukas -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/B270E5FC-1646-4C9C-8B6F-2CF0928E15B4%40pooteeweet.org. For more options, visit https://groups.google.com/d/optout.
