Skip to content

Commit 37b139d

Browse files
committed
🖍️ fixed additional typos
1 parent d51c6a2 commit 37b139d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/implementation_details.adoc

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ and the callback that match are encoded into a `stdx::bitset`.
1515

1616
However, once this initial representation is built, we then take this and
1717
perform additional work (at compile time) to encode the bitsets as RLE
18-
data, and store in the index just an offset into the blog of RLE data
18+
data, and store in the index just an offset into the blob of RLE data
1919
rather than the bitset itself.
2020

2121
This is good for message maps that contain a large number of handlers as
@@ -74,8 +74,8 @@ Specifics:
7474

7575
The `msg::rle_indexed_builder` will go through a process to take the indices and
7676
their bitset data and build a single blob of RLE encoded data for all indices, stored in
77-
and instance of a `msg::detail::rle_storage`. It also generates a set of
78-
`msg::detail::rle_index` entries for each of the index entries that maps the orignial bitmap
77+
an instance of a `msg::detail::rle_storage`. It also generates a set of
78+
`msg::detail::rle_index` entries for each of the index entries that maps the original bitmap
7979
to a location in the shared storage blob.
8080

8181
The `rle_storage` object contains a simple array of all RLE data bytes. The `rle_index`
@@ -85,7 +85,7 @@ offset to avoid wasted storage and use that.
8585
NOTE: The specific `rle_storage` and `rle_index`​s are locked together using a unique type
8686
so that the `rle_index` can not be used with the wrong `rle_storage` object.
8787

88-
When building the shared blog, the encoder will attempt to reduce the storage size by finding
88+
When building the shared blob, the encoder will attempt to reduce the storage size by finding
8989
and reusing repeated patterns in the RLE data.
9090

9191
The final `msg::indexed_handler` contains an instance of the `msg::rle_indices` which contains
@@ -95,7 +95,7 @@ This means that the final compile time data generated consists of:
9595

9696
- The Message Map lookups as per the normal implementation, however they store a simple offset
9797
rather than a bitset.
98-
- The blog of all RLE bitset data for all indices in the message handling map
98+
- The blob of all RLE bitset data for all indices in the message handling map
9999

100100
==== Runtime Handling
101101

@@ -108,13 +108,13 @@ a `msg::detail::rle_decoder` by the `rle_storage`. This converts the offset into
108108
pointer to the sequence of `std::byte`​s for the RLE encoding.
109109

110110
All the collected `rle_decoders` from the various maps in the set of indices are then passed
111-
to an instance of the `msg::detail::rle_interset` object and returned from the `rle_indices`
111+
to an instance of the `msg::detail::rle_intersect` object and returned from the `rle_indices`
112112
call operator.
113113

114114
The `rle_decoder` provides a single-use enumerator that will step over the groups of
115115
`0`​s or `1`​s, providing a way to advance through them by arbitrary increments.
116116

117-
The `rle_interset` implementation wraps the variadic set of `rle_decoder`​s so that
117+
The `rle_intersect` implementation wraps the variadic set of `rle_decoder`​s so that
118118
the caller can iterate through all `1`​s, calling the appropriate callback as it goes.
119119

120120
===== Efficient Iteration of Bits

0 commit comments

Comments
 (0)