on master help sign in
Merge pull request #37 from hussein-aitlahcen/docs

(WIP) docs: typos

commit4272abdc93a89a9049dcbda2bf40d5e49b0eb599 authorHarendra Kumar <harendra.kumar@gmail.com> dateTue 10 Apr 2018, 12:12 (9 years ago) parenta445ef98c53f8d
1 file changed+4−4
src/Streamly/Core.hs+4−4
src/Streamly/Core.hs+4−4
@@ -150,7 +150,7 @@ data SVar m a =
150150--
151151-- data Stream m a = Stop | Yield a (Maybe (Stream m a))
152152--
153−-- Our goal is to be able to represent finite as well infinite streams and
153+-- Our goal is to be able to represent finite as well as infinite streams and
154154-- being able to compose a large number of small streams efficiently. In
155155-- addition we want to compose streams in parallel, to facilitate that we
156156-- maintain a local state in an SVar that is shared across and is used for
@@ -184,7 +184,7 @@ data SVar m a =
184184--
185185-- Whenever we make a singleton stream or in general when we build a stream
186186-- strictly i.e. when we know all the elements of the stream in advance we can
187−-- use the last yield to indicate th end of the stream, because we know in
187+-- use the last yield to indicate the end of the stream, because we know in
188188-- advance at the time of the last yield that the stream is ending. We build
189189-- singleton streams in the implementation of 'pure' for Applicative and Monad,
190190-- and in 'lift' for MonadTrans, in these places we use yield with 'Nothing' to
@@ -531,7 +531,7 @@ toStreamVar sv m = do
531531-- if the consumer is running faster than us. As soon as we encounter an
532532-- Alternative composition we create a push pull pair of threads. We use a
533533-- channel for communication between the consumer pulling from the channel and
534−-- the producer who pushing to the channel. The producer creates more threads
534+-- the producer who is pushing to the channel. The producer creates more threads
535535-- if no output is seen on the channel, that is the consumer is running faster.
536536-- However this mechanism can be problematic if the initial production latency
537537-- is high, we may end up creating too many threads. So we need some way to
@@ -548,7 +548,7 @@ toStreamVar sv m = do
548548-- TBD the alternative composition allows us to dispatch a chunkSize of only 1.
549549-- If we have to dispatch in arbitrary chunksizes we will need to compose the
550550-- parallel actions using a data constructor (Free Alternative) instead so that
551−-- we can divide it in chunks of arbitrary size before dispatch. If the stream
551+-- we can divide it in chunks of arbitrary size before dispatching. If the stream
552552-- is composed of hierarchically composed grains of different sizes then we can
553553-- always switch to a desired granularity depending on the consumer speed.
554554--