Hey Benjamin On Wed, Jan 13, 2021 at 1:47 PM Benjamin Eberlei <kont...@beberlei.de> wrote:
> I get where you are coming from, but side-effect based > notices/deprecations is just the way PHP works at the moment and as such > this existing mechanism should be used and extended. > > I do have (vague) plans to tackle alternative ways to process > notices/deprecations in the future, but this is independent from that and > #[Deprecated] would automatically tie into a change of this kind. > If you have vague plans, perhaps introducing `#[Deprecated]` first, then proposing a separate RFC for the runtime behavior? For me, runtime behavior is: * a big problem with existing tools that started doing this * a production outage risk * something that attributes shouldn't do anyway, at least not out of the box (AOP OOTB is quite ugly and unexpected) As usual, I'm fighting for pushing things into compile-time rather than runtime, as runtime in PHP is already quite the nightmare of things to keep in mind. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/
