Impl Serialize/Deserialize for std::ops::{Bound, RangeFrom, RangeTo, RangeToInclusive}

[0nkery]

Implemented Serialize and Deserialize traits for various interval-related types from std.

Could help me to setup cfgs etc properly?

[dtolnay]

Could you explain more about your use case for these impls? How is all of this going to be used in what you are building?

[0nkery]

Hi. It's useful because Diesel uses (Bound<T>, Bound<T>) to represent Postgres ranges. We use one struct for queries and JSON ser/de so it seems like a good thing to have.

As for Range-types, I find it appropriate to use precise types for ranges (both with Diesel and Serde). Currently I propose changes to Diesel (diesel-rs/diesel#1971) to add the ability to use these types with Queryable.

Anyway, if you think that Range-types should not be added, I'm glad to revise PR.

[dtolnay]

It sounds like the two reasons for wanting the Bound impls is Diesel's choice of Bound to represent ranges and your code's choice of doing queries and json based on the same struct. What would be the impact on your code if we decide not to provide these impls in Serde? Probably you would need to apply a serialize_with / deserialize_with function on the field containing Bound right?

[0nkery]

Yep, that's right.

[dtolnay]

Thanks, I merged the PR but pared it down to just the Bound impls in a later commit. I am not opposed to the other impls but I would prefer not to accept code that I don't know of anyone wanting to use.

Published in 1.0.86.

[0nkery]

Thanks! We've decided to use Bound only anyway.