I wish that people would spend a tenth of the time actually profiling Cargo as they do talking about theoretical performance of dependency resolution.
Is exponential behavior not actually a risk here? Because if it is a risk, experience only tells you that you've not yet fallen over the exponential cliff, not that the cliff isn't out there waiting for you.
-
-
The idea that maybe, someday, an algorithm for solving a problem might theoretically cause a performance problem is a terrible reason to not even try to solve that problem in the first place.
-
Wow, Twitter really degrades this sort of conversation. I mean, I already said in other tweets that I thought that waiting until a problem arises seems perfectly reasonable here. This is just a point of curiosity as to what the future might hold.
End of conversation
New conversation -
-
-
Being able to include multiple versions of a package is the kind of thing that can invalidate the reduction to SAT and thus make it so that exponential behavior isn't a risk. But I don't know enough of the details to say either way.
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.