Hmmm, bad example. Assume memory instead. That said, reordering/
parallelization of *certain combinations of* writes/reads to
independent files under whole program analysis is no less safe than
sequential writes/reads. It just "feels" less safe, but the one thing
that will screw both up is interference from outside programs.
Regards,
John A. De Goes
N-Brain, Inc.
The Evolution of Collaboration
http://www.n-brain.net | 877-376-2724 x 101
On Aug 13, 2009, at 3:45 AM, Jason Dusek wrote:
2009/08/12 John A. De Goes <[email protected]>:
The next step is to distinguish between reading file A and
reading file B, between reading file A and writing file A,
between reading one part of file A and writing another part of
file A, etc. When the effect system can carry that kind of
information, and not just for files, but network, memory,
etc., then you'll be able to do some extremely powerful
parallelization & optimization.
I am challenged to imagine optimizations that would be safe in
the case of File I/O.
--
Jason Dusek
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe
