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.
-
how? you're still going to get those users PRing your project with diffs to support their target, and they'll probably be displeased if you regress on their contributions.
Yeah, it is solved. The builds are external to the project, so it puts no burden on the project owner. The cost is potential fragmentation, of course, but it's a tradeoff.
-
-
(That does assume that the required changes for each new target are entirely in the build, and not in the source.)
-
also, how do you maintain an external build setup? nightly validation against master? pin it with git submodules and actively bump?
- Show replies
New conversation -
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.