On 1-5-2022 9:54, Rowan Tommins wrote:
On 1 May 2022 03:49:11 BST, Juliette Reinders Folmer
wrote:
As far as I understand it, if the deprecation notice is **only** thrown for the
deprecated callables, the code can always be adjusted to use the recommended
replacement code patterns as per
On 29/04/2022 03:04, Juliette Reinders Folmer wrote:
And that's basically exactly what I already did which led me to
discover the patterns I posted about as they looked concerning (though
I didn't use Nikic's tool, but the WIP PHPCompatibility sniff)...
I scanned a significant number of
On 28-4-2022 21:42, Rowan Tommins wrote:
On 28/04/2022 15:09, Juliette Reinders Folmer wrote:
Ah! So you're basically asking for the impossible. Search for a code
pattern where a deprecation would not be useful, while noone has been
able to come up with one.
Not at all. I'm saying look at
On 22-4-2022 8:47, Rowan Tommins wrote:
On 22 April 2022 02:02:58 BST, php-internals_nos...@adviesenzo.nl wrote:
I agree it would be a good idea to run a package analysis, but to be fair, in
all honesty that should have been done for the original RFC, which was
completely missing an impact
