in sea-query-binder, the time crate version is set as <0.3.35 (i.e., time = { version = "<0.3.35",...}).
Is there any reason for this?
It does cause some understandably unforeseen behavior when the lib/app code relies on 0.3.
It seems to work, but tools like cargo outdated completely break for example, and might have other side effects.
Steps to Reproduce
Have sea-query with sea-query-binder with time
have another time = "0.3' in the Cargo.toml
cargo install cargo-outdated and then cargo outdated. The issue is that if this break, there might be more side effecs.
tyt2y3
commented
4 months ago
Description
In
sea-query-binderversion0.6.0-rc.2,in sea-query-binder, the
timecrate version is set as<0.3.35(i.e.,time = { version = "<0.3.35",...}).Is there any reason for this?
It does cause some understandably unforeseen behavior when the lib/app code relies on
0.3. It seems to work, but tools likecargo outdatedcompletely break for example, and might have other side effects.Steps to Reproduce
time = "0.3'in theCargo.tomlcargo install cargo-outdatedand thencargo outdated. The issue is that if this break, there might be more side effecs.Expected Behavior
timeset to version0.3or0.3.35.Actual Behavior
timeset to version<0.3.35.Versions
In
sea-query-binderversion0.6.0-rc.2,