I hate it when they remove functionality from a crate that you used a lot and you have to switch to a different crate, rewriting half of your application, because the new crate has quite a different API.
Which crates are you referring to? In general, my experience with adapting to a different dependency has been quite smooth so far, so I'm interested in seeing a counter-example.
The time crate had a strftime-compliant function to format time into a string. I relied heavily on it, but it was removed in one of the 0.2.x minor releases. I went with chrono and its format function instead. The time::strftime function had a Result return value, the chrono version returns a DelayedFormat, so I had to rewrite all the Result checks.
Ah ok thanks. Removing functionality in a minor release is of course not semver compatible, so that's a no-go. Never used the time crate, have been using chrono ever since I remember working with that kind of functionality.
The application (a small blog server) was one of my first non-"hello world" contacts with Rust (I think it's nearly 5 years old now) so I went with what I found first 😁 Nowadays I would choose chrono over time, because it seems closer to what I'm used from other languages.
silwol
•In general, my experience with adapting to a different dependency has been quite smooth so far, so I'm interested in seeing a counter-example.
Victor von Void
•The time::strftime function had a Result return value, the chrono version returns a DelayedFormat, so I had to rewrite all the Result checks.
silwol
•Victor von Void
•