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.
-
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?
-
It's manual updates. Builds may be defined in terms of commits, tags or branches in either project (i.e. code) or overlay (i.e. build) repositories, and Fury can automate git updates you depend on (but it will only let you publish against commits).
End of conversation
New conversation -
-
-
that's the big if.
-
There's another "big if": can I actually represent builds using my data-only model...
End of conversation
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.