Skip to content

Commit 5b03f86

Browse files
committed
fix: escaping <> tag
1 parent 87ba0ce commit 5b03f86

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

docs/artificialintelligence/assignments/maze/maze-datastructure.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ struct RoomRegistry {
175175
};
176176
```
177177

178-
Before going deep into how can we address the indexes for the walls, you need to know vector<bool> are not common vectors where each element returns a reference to a bool. Instead, it returns a proxy object that behaves like a bool. This is because the standard vector<bool> is a specialization of the vector class that is optimized for space efficiency.
178+
Before going deep into how can we address the indexes for the walls, you need to know `vector<bool>` are not common vectors where each element returns a reference to a bool. Instead, it returns a proxy object that behaves like a bool. This is because the standard `vector<bool>` is a specialization of the vector class that is optimized for space efficiency.
179179

180180
```c++
181181
// Example of how vector<bool> works
@@ -191,7 +191,7 @@ stuct vector<bool> {
191191

192192
![img_1.png](img_1.png)
193193

194-
Now we have a way to address bits directly using vector<bool>, but you need to remember that for an X x Y grid, we will need X+1 vertical walls and Y+1 horizontal walls. Check the following example below for a 2x2 grid:
194+
Now we have a way to address bits directly using `vector<bool>`, but you need to remember that for an X x Y grid, we will need X+1 vertical walls and Y+1 horizontal walls. Check the following example below for a 2x2 grid:
195195

196196
```
197197
_ _
@@ -201,7 +201,7 @@ Now we have a way to address bits directly using vector<bool>, but you need to r
201201

202202
So we will need 3 vertical walls and 3 horizontal walls.
203203

204-
Now, we reached to the next issue. How can we address the walls in the std::vector<bool>? We will need to change our point of view from addressing Rooms at position (X,Y) to WallIntersections. Every intersection will be 2 bits to represent vertical and horizontal walls.
204+
Now, we reached to the next issue. How can we address the walls in the `std::vector<bool>`? We will need to change our point of view from addressing Rooms at position (X,Y) to WallIntersections. Every intersection will be 2 bits to represent vertical and horizontal walls.
205205

206206
```
207207
_ _
@@ -277,4 +277,4 @@ struct RoomRegistry {
277277
278278
## Conclusion
279279
280-
Now we are using the most memory efficient way to represent a dense maze. We learned matrix flattening, bit index addressing, data layout, and discovered why vector<bool> is a bit different from other vectors.
280+
Now we are using the most memory efficient way to represent a dense maze. We learned matrix flattening, bit index addressing, data layout, and discovered why `vector<bool>` is a bit different from other vectors.

0 commit comments

Comments
 (0)