Hacker News new | past | comments | ask | show | jobs | submit login

Wouldn’t this still break a consumer who doesn’t realize the trick is being employed? Doesn’t this assume the consumer is making the requisite changes in their library as part of upgrading to the “nonbreaking” upgrade that slips the new type definition in via its dependency on its own breaking upgrade?



No. Someone using the old version can continue using it, completely unaware of the fact that anything changed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: