Re: [MirageOS-devel] Using Result instead of Option in libraries

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 14 Oct 2016, at 15:11, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
> 
> On 14/10/2016 15:08, Anil Madhavapeddy wrote:
>> Yeah, once we agree on the conventions :-)  Once we have everything using 
>> Result.t, we also need to find the right set of combinators.
>> 
>> - There is Rresult for basic Result.t handling: 
>> http://erratique.ch/software/rresult/doc/Rresult.html
>> - Lwt_result has a slightly different set of combinators 
>> https://github.com/ocsigen/lwt/blob/master/src/core/lwt_result.mli
>> 
>> So I guess we need to decide if we publish an Rresult_lwt.t which lifts up 
>> "('a,'b) result" into an Lwt.t with the same API as Rresult otherwise.
> 
> Based on earlier discussion from January 2015, I put some combinators in
> mirage-types.lwt (maybe they should live elsewhere)
> https://github.com/hannesm/mirage/blob/network-error/types/runtime.lwt/m_infix.mli

Ah, missed those, thanks!

Looks like we have a number of different conventions for the binds.  Do we want 
to have the same set of operators with and without Lwt support (and open the 
Infix module locally as needed) or separate operators that be used alongside 
each other?

Anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel