I don't quite like this API, something like https://docs.rs/sea-query/latest/sea_query/query/struct.SelectStatement.html#method.conditions would serve a more general usecase, may be something like:

fn maybe<T, F>(&mut self, val: Option<T>, if_some: F)
where F: FnOnce(&mut Self, v: T)

In any case I think fn foo<T>(param: T) where T: Into<Option<u64>> will do the trick better.

Hey @tyt2y3, check check #1415 for the maybe API

I still think making limit and offset to accept Into<Option<u64>> is worth doing. @tyt2y3 please advice

I think the API behaviour here should be if None is passed in, it should clear the limit/offset instead of no-op.

I think the API behaviour here should be if None is passed in, it should clear the limit/offset instead of no-op.

Yes, you're right! How could I miss that. Let me add that in.

That's why I said the original intention is handled better by the apply_if API instead of this one

Still hesitated on publishing this API?