[Swift-commit] r3874 - text/parco10submission

noreply at svn.ci.uchicago.edu noreply at svn.ci.uchicago.edu
Thu Jan 6 15:32:47 CST 2011


Author: dsk
Date: 2011-01-06 15:32:47 -0600 (Thu, 06 Jan 2011)
New Revision: 3874

Modified:
   text/parco10submission/paper.tex
Log:
adding a comment


Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-06 21:29:35 UTC (rev 3873)
+++ text/parco10submission/paper.tex	2011-01-06 21:32:47 UTC (rev 3874)
@@ -1779,7 +1779,7 @@
 techniques and employing an internal IP network.
 
 \mikenote{In order to achieve automatic parallelization in Swift, instead of using thunks (i.e., suspended computations), which yield lazy
-evaluation, we employ futures, which result in eager parallelism. In this process, we trade the ability to efficiently deal with infinite structures for the ability to minimize computation time. It must, however, be noted that a middle ground exists: lazy futures (futures whose computation is delayed until a value is first needed).}
+evaluation, we employ futures, which result in eager parallelism. In this process, we trade the ability to efficiently deal with infinite structures for the ability to minimize computation time. It must, however, be noted that a middle ground exists: lazy futures (futures whose computation is delayed until a value is first needed).} \katznote{this is very confusing to me - it's mixing too many concepts and overloading lazy and eager.}
 
 \subsection{Filesystem access optimizations}
 




More information about the Swift-commit mailing list