`CCOption.bind` and `CCParse.bind` have inconsistent parameter orders; should be unified?

[torch-and-blanket]

Depending on this project's attitude toward breaking changes, it may be worth changing CCOption.bind : 'a option -> ('a -> 'b option) -> 'b option to align with the current type of CCParse.bind : ('a -> 'b CCParse.t) -> 'a CCParse.t -> 'b CCParse.t. I suggest this, rather than vice versa, to facilitate patterns like return x |> bind f |> bind g, following the general principle that a function's final argument should be the argument to which that function is least likely to be "partially" applied.

Making the types of all bind functions consistent throughout the library will make it easier to write functors that expect monads as well and help keep interfaces to CC modules predictable. As far as I can tell, these two are the only instances of bind throughout containers.

[c-cube]

I think that means that CCParse.bind is the wrong one, tbh. In general I use the infix operators anyway.

[torch-and-blanket]

Thanks, quick reply!

Are you open to one of those functions changing, then? At least in principle?

I'm also curious what your reason for preferring 'a t -> ('a -> 'b t) -> 'b t is, over the other way round.

[c-cube]

I think I started this way because of Lwt.bind a long time ago. As I say, it's better to use let* these days :-).