If you go the source dependencies way, you cannot add a public method to any of your types, ever. Because that breaks backward source compatibility. Yes, binary compatibility is hard. But source compatibility is *impossible*.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Yeah somehow the effect has been completely wrong. But I never set out to pretend bincompat was *easy*. It *is* hard. My point was: a) forget about source compat because it's way worse (and you don't realize it) and b) here are tools and methods to correctly design for bincompat.
FWIW, the talk is a really great exploration of the challenges of binary compatibility, and has some good examples of binary-incompatible changes which aren't at all obvious.
-
-
and a proven, slam dunk one about source-incompatible changes
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.