Random nugget of insight from @sjrdoeraene found while perusing unrelated threads: Source compatibility is broken in Scala when you *add a public method to a type*. Even ignoring diamonds, this alone is murder on source dependency schemes in this language.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Ah but if the entire ecosystem were to move to something like Fury or similar, then suddenly source compatibility becomes more important than binary compatibility.
Fury deliberately takes an approach to try to mitigate this problem, though: No build definition gets silently upgraded to a different version of the source from what it was published with. Of course, that creates a new problem of more conflicts to resolve...
-
-
...which it attempts to minimize using multi-tiered layers for publishing coherent collections of projects with dependencies resolved. It shares the problem of conflict-resolution across the whole community, and hopefully reduces duplication of effort.
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.