In other words: Yes, updating dependencies can cause problems. The answer is not to make it hard to update dependencies.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The key point, no matter what name you want to use, is that documenting incompatibilities doesn't actually *solve* anything either. Unless you can rewrite the past and document new incompatibilities in old packages, which has its own problems (and isn't happening anyway).
-
Yes, it does. Specifying incompatibilities makes cargo update do the right thing instead of breaking your code.
- 3 more replies
New conversation -
-
-
I've been thinking about this for the last day and I think he actually has two good points, buried underneath a lot of fluff. The first one is the claim that, from the UI perspective, each major version living in its own package / repo is a good thing. I think it's interesting…
-
to explore (even if your package manager allows concurrent installations!) but ultimately fundamentally irrelevant to dependency resolution, so let's ignore that for the moment. The second one is that minimum version selection is valuable because it exposes underconstrained…
- 6 more replies
New conversation -
-
-
"it just makes things that should be easy hard" is Go in a nutshell tbh
-
on the contrary, the idea behind Rust seems to make things complicated that should be simple
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.