Skip to content

Commit e1444da

Browse files
committed
TOSQUASH typos
1 parent 215a0ec commit e1444da

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

ouroboros-consensus/src/unstable-consensus-testlib/Test/CsjModel.hs

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ data CsjClientState p = CsjClientState {
9494
-- | the greatest point the peer has accepted as part of a jump
9595
--
9696
-- If 'latestJump' is 'Origin', then this is the immutable tip as of when
97-
-- the peer connected (and so is the Dynamo's, which means the Dynamo'S
97+
-- the peer connected (and so is the Dynamo's, which means the Dynamo's
9898
-- 'comm' cannot be any younger than this peer's 'comm').
9999
comm :: !(WithOrigin p)
100100
}
@@ -183,8 +183,8 @@ trimCandidate y =
183183

184184
-- | A 'MsgFindIntersect' for 'comm'
185185
--
186-
-- minor optimization opportunity: if the Jumpers latest response was
187-
-- @MsgIntersectionFound@ then this could be 'NoReset'.
186+
-- Minor optimization opportunity: if the Jumper's latest response was
187+
-- @MsgIntersectionFound@ then this could be skipped.
188188
promotionMessage :: CsjClientState p -> CsjReaction p
189189
promotionMessage = MsgFindIntersect . comm
190190

@@ -269,12 +269,12 @@ nextMsgFindIntersect2 bi =
269269
-- Dynamo, and so by offering the whole jump in the first message,
270270
-- load on honest Jumpers is minimized: one message per jump.
271271
Just{} -> neMid nyd
272-
-- TODO At least for the reference Haskell Cardano node, each
273-
-- additional point in the 'MsgFindIntersect' message is most
274-
-- negligible unless they're in different ImmDB chunk files. So
275-
-- this logic here could include more points (perhaps once all of
276-
-- @nyd@ is in the same chunk file) in order to ensure the
277-
-- bisection requires fewer round trips while only increasing the
272+
-- TODO At least for the reference Haskell Cardano node, the cost
273+
-- of each additional point in the 'MsgFindIntersect' message is
274+
-- mostly negligible unless they're in different ImmDB chunk files.
275+
-- So this logic here could include more points (perhaps once all
276+
-- of @nyd@ is in the same chunk file) in order to ensure the
277+
-- bisection requires fewer round trips while increasing the
278278
-- upstream per-message cost only negligibly.
279279
where
280280
nyd = notYetDetermined bi

ouroboros-consensus/src/unstable-consensus-testlib/Test/CsjModel/NonEmptySeq.hs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ data BinarySearchResult =
6262

6363
neBinarySearch :: (a -> Bool) -> NonEmptySeq a -> BinarySearchResult
6464
neBinarySearch predicate (UnsafeNonEmptySeq xs) =
65-
finish $ go l0 r0
65+
finish $ go l0 r0
6666
where
6767
l0 = negate 1
6868
r0 = length xs

0 commit comments

Comments
 (0)