A lengthy Slack discussion brought us to the thoughts that: * both the *string* typehint and the *static* return type issues should make us wait until *PHP8* to incorporate those changes in the PSR interfaces
* at a minimum, in PHP7, this would mean doing the previously proposed typehint upgrade *without* *string*, followed by the return type upgrade *without* *self*/*static*... and then a *third* upgrade in *PHP8* to do *string* typehints and *static* return types * though some might choose to do the typehint upgrade without *string* pre- *PHP8*, potentially many would then wait until *PHP8* to do *one* return type upgrade that included *static*... with *string* typehints conveniently tagging along * with *PHP8* scheduled for later this year, maybe it's cleaner to *just wait on all PSR upgrades* until *PHP8*, so that no special treatment is required in the upgrades Again, it is the headaches from the *string* typehints (and its *Stringable* entanglements) along with the *static* return (the proper choice for the earlier *self* use cases) that makes it problematic to include these two in *PHP7*. What does everything think about going with the overall *wait-for-PHP8* approach? CRB -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/930707db-1ce7-4050-bc8e-1f846893362b%40googlegroups.com.
