I'm wondering if specifying non-linear version ranges for a dependency is possible in Cargo.
I'm developing a library that has a dependency on library
foo which manages a legacy (1.0) and stable (1.1) channel. Recently, a bug was found in the
foo library and they had to change public APIs to mitigate this issue. Let's say the fix became live in 1.0.x and 1.1.y.
Now, I would like to specify that my library works for
foo with version ranges (>= 1.0.x, < 1.1.0) and (>= 1.1.y). How can I express this in Cargo?