Maybe that was unclear (I wrote this in a rush), but this blog post is about how you can implement that part of SemVer (deprecating part of your public API) for php types. Not sure what "It" is referring to in "It's not an implementation issue IMO" or why you two attempt to teach me the basics of SemVer when I'm trying to show how to put it in practice for a specific part of a PHP API.
Ah, with "it" i mean deprecating a type in php. As far as i'm concerned this is enough:
* @deprecated please use ShinyNewFoo instead!
But i also accept the fact that i may have missed some point in this article...
This solution is enough in some situations. In others, you will need inheritance, and in some more complicated situations, you will have to resort to class aliases. That's what I failed to make perfectly clear in my article.
We’re a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.