Because you don't want to break the existing consuming, and most importantly the implementing code.
You didn't break it on paper, i.e. it's binary-compatible, but not semantically compatible, since you still have to update existing code to use the new API correctly.
I agree, that's misunderstandable on my end. The point is that you can use the new API. Using it doesn't break the old implementation
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Because you don't want to break the existing consuming, and most importantly the implementing code.
You didn't break it on paper, i.e. it's binary-compatible, but not semantically compatible, since you still have to update existing code to use the new API correctly.
I agree, that's misunderstandable on my end. The point is that you can use the new API. Using it doesn't break the old implementation