c0a93a4 · streamly · git.iko.soy

git.iko.soy/streamly

Fix some easy-to-make typos

commitc0a93a40337319fdea3a97dbf98bfc68f45cd5a7 authorBrian Wignall <brianwignall@gmail.com> dateMon 25 Nov 2019, 13:50 (7 years ago) parent50b7824

15 files changed+21−21

compare with master

unifiedsplit

CONTRIBUTING.md+1−1 Changelog.md+1−1 bench.sh+2−2 design/module-organization.md+1−1 design/utf8-decoder.md+3−3 examples/ControlFlow.hs+1−1 src/Streamly.hs+1−1 src/Streamly/Data/Fold.hs+1−1 src/Streamly/Internal/Data/Pipe.hs+2−2 src/Streamly/Internal/Data/SVar.hs+2−2 src/Streamly/Internal/FileSystem/File.hs+1−1 src/Streamly/Internal/Prelude.hs+2−2 src/Streamly/Prelude.hs+1−1 src/Streamly/Streams/Serial.hs+1−1 src/Streamly/Streams/StreamD.hs+1−1

CONTRIBUTING.md+1−1

@@ -191,7 +191,7 @@ folds where there is no incoming state, we start with the initial state

191191

1921921. When we are building a concurrent stream that needs to share the same `SVar`

193193 we pass the incoming state as is.

194−2. In all other cases we must not share the SVar and everytime we pass on the

194+2. In all other cases we must not share the SVar and every time we pass on the

195195 state to run a stream we must use `rstState` to reset the `SVar` in the

196196 state.

197197

Changelog.md+1−1

@@ -355,7 +355,7 @@ concurrently using this.

355355* Add `iterate`, `iterateM` stream operations

356356

357357### Bug Fixes

358−* Fixed a bug that casued unexpected behavior when `pure` was used to inject

358+* Fixed a bug that caused unexpected behavior when `pure` was used to inject

359359 values in Applicative composition of `ZipStream` and `ZipAsync` types.

360360

361361## 0.1.1

bench.sh+2−2

@@ -21,7 +21,7 @@ print_help () {

2121 echo "commit is generated, in the 'charts' directory."

2222 echo "Use --base and --candidate to select the commits to compare."

2323 echo

24− echo "Any arguments after a '--' are passed directly to guage"

24+ echo "Any arguments after a '--' are passed directly to gauge"

2525 exit

2626}

2727

@@ -86,7 +86,7 @@ build_report_progs() {

8686

8787# We run the benchmarks in isolation in a separate process so that different

8888# benchmarks do not interfere with other. To enable that we need to pass the

89−# benchmark exe path to guage as an argument. Unfortunately it cannot find its

89+# benchmark exe path to gauge as an argument. Unfortunately it cannot find its

9090# own path currently.

9191

9292# The path is dependent on the architecture and cabal version.

design/module-organization.md+1−1

@@ -1,6 +1,6 @@

11# Internal vs External

3−We keep all modules exposed to faciliate convenient exposure of experimental

3+We keep all modules exposed to facilitate convenient exposure of experimental

44APIs and constructors to users. It allows users of the library to experiment

55much more easily and carry a caveat that these APIs can change in future

66without notice. Since everything is exposed, maintainers do not have to think

design/utf8-decoder.md+3−3

@@ -139,7 +139,7 @@ null-terminated UTF-8 encoded string.

139139

140140### Error recovery

141141

142−It is sometimes desireable to recover from errors when decoding strings

142+It is sometimes desirable to recover from errors when decoding strings

143143that are supposed to be UTF-8 encoded. Programmers should be aware that

144144this can negatively affect the security properties of their application.

145145A common recovery method is to replace malformed sequences with a

@@ -155,8 +155,8 @@ aswell.

155155

156156The following code implements one such recovery strategy. When an

157157unexpected byte is encountered, the sequence up to that point will be

158−replaced and, if the error occured in the middle of a sequence, will

159−retry the byte as if it occured at the beginning of a string. Note that

158+replaced and, if the error occurred in the middle of a sequence, will

159+retry the byte as if it occurred at the beginning of a string. Note that

160160the decode function detects errors as early as possible, so the sequence

161161`0xED 0xA0 0x80` would result in three replacement characters.

162162

examples/ControlFlow.hs+1−1

@@ -69,7 +69,7 @@ mainMaybeBelow = do

6969-- of non-determinism below.

7070--

7171-- Note that this is redundant configuration as the same behavior can be

72−-- acheived with just streamly, using mzero.

72+-- achieved with just streamly, using mzero.

7373--

7474getSequenceMaybeAbove :: (IsStream t, MonadIO (t m)) => MaybeT (t m) ()

7575getSequenceMaybeAbove = do

src/Streamly.hs+1−1

@@ -236,7 +236,7 @@ import qualified Streamly.Prelude as P

236236import qualified Streamly.Internal.Prelude as IP

237237import qualified Streamly.Streams.StreamK as K

238238

239−-- XXX provide good succinct examples of pipelining, merging, splitting ect.

239+-- XXX provide good succinct examples of pipelining, merging, splitting etc.

240240-- below.

241241--

242242-- $streams

src/Streamly/Data/Fold.hs+1−1

@@ -190,7 +190,7 @@ module Streamly.Data.Fold

190190 -- ...

191191 -- @

192192 --

193− -- To compute the average of numbers in a stream without going throught he

193+ -- To compute the average of numbers in a stream without going through the

194194 -- stream twice:

195195 --

196196 -- >>> let avg = (/) <$> FL.sum <*> fmap fromIntegral FL.length

src/Streamly/Internal/Data/Pipe.hs+2−2

@@ -141,7 +141,7 @@ module Streamly.Internal.Data.Pipe

141141 -- ...

142142 -- @

143143 --

144− -- To compute the average of numbers in a stream without going throught he

144+ -- To compute the average of numbers in a stream without going through the

145145 -- stream twice:

146146 --

147147 -- >>> let avg = (/) <$> FL.sum <*> fmap fromIntegral FL.length

@@ -1805,7 +1805,7 @@ classifyKeepAliveChunks spanout = classifyChunksBy spanout True

18051805-- All the input elements belonging to a session are collected using the fold

18061806-- @f@. The session key and the fold result are emitted in the output stream

18071807-- when the session is purged either via the session close event or via the

1808−-- session liftime timeout.

1808+-- session lifetime timeout.

18091809--

18101810-- @since 0.7.0

18111811{-# INLINABLE classifySessionsBy #-}

src/Streamly/Internal/Data/SVar.hs+2−2

@@ -1674,7 +1674,7 @@ estimateWorkers workerLimit svarYields gainLossYields

16741674 -- maxWorkerLatency.

16751675 --

16761676 let

1677− -- How many workers do we need to acheive the required rate?

1677+ -- How many workers do we need to achieve the required rate?

16781678 --

16791679 -- When the workers are IO bound we can increase the throughput by

16801680 -- increasing the number of workers as long as the IO device has enough

@@ -1691,7 +1691,7 @@ estimateWorkers workerLimit svarYields gainLossYields

16911691 -- use that to determine the max rate of workers, and also take the CPU

16921692 -- bandwidth into account. We can also discover the IO bandwidth if we

16931693 -- know that we are not CPU bound, then how much steady state rate are

1694− -- we able to acheive. Design tests for CPU bound and IO bound cases.

1694+ -- we able to achieve. Design tests for CPU bound and IO bound cases.

16951695

16961696 -- Calculate how many yields are we ahead or behind to match the exact

16971697 -- required rate. Based on that we increase or decrease the effective

src/Streamly/Internal/FileSystem/File.hs+1−1

@@ -22,7 +22,7 @@

2222-- session consisting of multiple reads and writes to the handle, these APIs

2323-- are one shot read or write APIs. These APIs open the file handle, perform

2424-- the requested operation and close the handle. Thease are safer compared to

25−-- the handle based APIs as there is no possiblity of a file descriptor

25+-- the handle based APIs as there is no possibility of a file descriptor

2626-- leakage.

2727--

2828-- > import qualified Streamly.Internal.FileSystem.File as File

src/Streamly/Internal/Prelude.hs+2−2

@@ -2077,7 +2077,7 @@ insertBy cmp x m = fromStreamS $ S.insertBy cmp x (toStreamS m)

20772077-- Deleting

20782078------------------------------------------------------------------------------

20792079

2080−-- | Deletes the first occurence of the element in the stream that satisfies

2080+-- | Deletes the first occurrence of the element in the stream that satisfies

20812081-- the given equality predicate.

20822082--

20832083-- @

@@ -3644,7 +3644,7 @@ classifyKeepAliveChunks spanout = classifyChunksBy spanout True

36443644-- All the input elements belonging to a session are collected using the fold

36453645-- @f@. The session key and the fold result are emitted in the output stream

36463646-- when the session is purged either via the session close event or via the

3647−-- session liftime timeout.

3647+-- session lifetime timeout.

36483648--

36493649-- @since 0.7.0

36503650{-# INLINABLE classifySessionsBy #-}

src/Streamly/Prelude.hs+1−1

@@ -781,7 +781,7 @@ import Streamly.Internal.Prelude

781781-- left fold reconstructs in a LIFO style, thereby reversing the order of

782782-- elements..

783783-- 3. A right fold has termination control and therefore can terminate early

784−-- without going throught the entire input, a left fold cannot terminate

784+-- without going through the entire input, a left fold cannot terminate

785785-- without consuming all of its input. For example, a right fold

786786-- implementation of 'or' can terminate as soon as it finds the first 'True'

787787-- element, whereas a left fold would necessarily go through the entire input

src/Streamly/Streams/Serial.hs+1−1

@@ -308,7 +308,7 @@ instance IsStream WSerialT where

308308------------------------------------------------------------------------------

309309

310310-- Additionally we can have m elements yield from the first stream and n

311−-- elements yeilding from the second stream. We can also have time slicing

311+-- elements yielding from the second stream. We can also have time slicing

312312-- variants of positional interleaving, e.g. run first stream for m seconds and

313313-- run the second stream for n seconds.

314314--

src/Streamly/Streams/StreamD.hs+1−1

@@ -579,7 +579,7 @@ enumerateFromThenIntegral from next =

579579-- 9007199254740992 + 2 :: Double => 9.007199254740994e15

580580

581581-- Instead we accumulate the increment counter and compute the increment

582−-- everytime before adding it to the starting number.

582+-- every time before adding it to the starting number.

583583--

584584-- This works for Integrals as well as floating point numbers, but

585585-- enumerateFromStepIntegral is faster for integrals.