From 1982c37f76c5df11f697c68041dcca28ada62592 Mon Sep 17 00:00:00 2001
From: Pedro Gonnet <gonnet@google.com>
Date: Tue, 12 Apr 2016 21:18:59 +0200
Subject: [PATCH] clearer wording on why we built our own task-based library.

---
 theory/paper_pasc/pasc_paper.tex | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/theory/paper_pasc/pasc_paper.tex b/theory/paper_pasc/pasc_paper.tex
index d06c535887..143c33ee1e 100644
--- a/theory/paper_pasc/pasc_paper.tex
+++ b/theory/paper_pasc/pasc_paper.tex
@@ -342,13 +342,14 @@ SMP~Superscalar \cite{ref:SMPSuperscalar}, OpenMP~3.0 \cite{ref:Duran2009},
 Intel's TBB \cite{ref:Reinders2007}, and, to some extent,
 Charm++ \cite{ref:Kale1993}.
 
-For convenience, and to make experimenting with different scheduling
-techniques easier, we chose to implement our own task scheduler
+Since none of these existing taks-based libraries provide the flexibility
+required to make experiment with different scheduling and communication
+techniques, we chose to implement our own task scheduler
 in \swift, which has since been back-ported as the general-purpose
 \qs task scheduler \cite{gonnet2013quicksched}.
 This also allowed us to extend the scheduler with the concept of
 task conflicts and integrate the asynchronous communication
-scheme described below.
+scheme described further on.
 
 Despite its advantages, and the variety of implementations,
 task-based parallelism is rarely used in
-- 
GitLab