# #[Deprecated] Attribute

- Thread: https://externals.io/message/127486
- Original archive: https://news-web.php.net/php.internals/127486
- Started by Ben Ramsey on 2025-05-27T19:04:56+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #127486 — Ben Ramsey — 2025-05-27T19:04:56+00:00

URL: https://externals.io/message/127486#127486

> 
> 
> 
> 
> > […]
> 
> I want to keep #[Deprecated] on other elements than functions / methods out
> of this RFC, because they require entirely different implementation
> approaches.
> 
> We identified in the PR already that this should at some point be
> standardized in core, because internal attributes will currently not be
> able to support extension through inheritance by userland for
> implementation reasons.
> 
> My next RFC update will reflect this future scope.


Last night, I identified a need for `#[Deprecated]` on a userland class in one of my libraries, but I had to settle on `@deprecated` for the widest range of compatibility.

Has there been anymore thought on putting together an implementation for this? I’m happy to draft an RFC if someone is able to help with the implementation. I don’t understand the complexities around the implementation, but is this something that could make it into 8.5, provided an RFC vote passes?

Cheers,
Ben