@@ -15,7 +15,7 @@ and the callback that match are encoded into a `stdx::bitset`.
15
15
16
16
However, once this initial representation is built, we then take this and
17
17
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
19
19
rather than the bitset itself.
20
20
21
21
This is good for message maps that contain a large number of handlers as
@@ -74,8 +74,8 @@ Specifics:
74
74
75
75
The `msg::rle_indexed_builder` will go through a process to take the indices and
76
76
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
79
79
to a location in the shared storage blob.
80
80
81
81
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.
85
85
NOTE: The specific `rle_storage` and `rle_index`s are locked together using a unique type
86
86
so that the `rle_index` can not be used with the wrong `rle_storage` object.
87
87
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
89
89
and reusing repeated patterns in the RLE data.
90
90
91
91
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:
95
95
96
96
- The Message Map lookups as per the normal implementation, however they store a simple offset
97
97
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
99
99
100
100
==== Runtime Handling
101
101
@@ -108,13 +108,13 @@ a `msg::detail::rle_decoder` by the `rle_storage`. This converts the offset into
108
108
pointer to the sequence of `std::byte`s for the RLE encoding.
109
109
110
110
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`
112
112
call operator.
113
113
114
114
The `rle_decoder` provides a single-use enumerator that will step over the groups of
115
115
`0`s or `1`s, providing a way to advance through them by arbitrary increments.
116
116
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
118
118
the caller can iterate through all `1`s, calling the appropriate callback as it goes.
119
119
120
120
===== Efficient Iteration of Bits
0 commit comments