Jean-Christophe Filliatre

> The fact that `MaxQueue` has a function called `pop_min` that pops the... maximum element may be found confusing Indeed. One solution would be to have two signatures `MinPQ` and...

Regarding the use of `Dynarray` unsafe operations, I now understand that my request was only meaningful for sequential code. I guess we can forget it.

Many thanks @gasche and @dbuenzli for your feedback on this PR! I'll be happy to make any change once we converge on some API. Notes: * I'm perfectly fine leaving...

Thanks again for your comments and suggestions. I'm also fine with `type 'a elt = priority * 'a` and the idea of giving up with curried functions. After all, pairs...

Hi @gasche and @dbuenzli , Many thanks once again for your detailed reviews and suggestions. I have adopted (mostly) the proposal of @dbuenzli . Here are the main changes: *...

> Thanks @backtracking. Re-reading five days later our discussion with @gasche on the gist I think I'm starting to bias towards his proposal [...] Sorry if this comment comes out...

> I wonder if we can get rid of the `Min/Max` distinction, let the comparator decide the order, and call the "best" element the `top` of the queue? Thanks for...

> I considered proposing that we move the comparator dispatch to runtime, and then even the distinction for polymorphic elements goes away, so there's no functors at all: > >...

With Cores, master and workers communicate using regular files and OCaml's input/output_value functions. So I see no reason why large values are an issue here. -- Jean-Christophe On 22/03/2017 12:03,...

I could reproduce it, i.e., I indeed get messages such as master: ** PID 20577 killed or stopped! ** These are workers from the previous computation (the one you stopped...