Version française
Home     About     Download     Resources     Contact us    
Browse thread
Objective Caml release 3.08.2
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Frédéric_Gava <frederic.gava@w...>
Subject: Re: [Caml-list] Objective Caml release 3.08.2
----- Original Message -----
From: "Damien Doligez" <damien.doligez@inria.fr>
To: "caml announce" <caml-announce@inria.fr>
Sent: Wednesday, November 24, 2004 2:06 PM
Subject: [Caml-list] Objective Caml release 3.08.2


> - stdlib: wrong order in Set.fold (PR#3161)

Why an order for the fold operator ? The fold operator is used in many
parallel applications and in these cases, the order is not specified (it is
done in parallel). Peraps add a new operator to the interface (scan ? or
async_fold ?) where the order is unspecified (another set's operators like
choose do not specified the order). In this case, it would be possible to
write a true parallel implementation of fold (every process "folds" a part
of the set and them they "fold" there tempory results) .

Frédéric Gava.