diff --git a/docs/ch03/regular_backgrounds.html b/docs/ch03/regular_backgrounds.html index 3c0f571..5fcace1 100644 --- a/docs/ch03/regular_backgrounds.html +++ b/docs/ch03/regular_backgrounds.html @@ -248,23 +248,10 @@ GBA's CPU can't do any of that. On the GBA, there's a genuine speed dif between looping over indexes and then indexing each loop (slow) compared to using an iterator that just stores an internal pointer and does +1 offset per loop until it reaches the end (fast). The repeated indexing itself can by itself -<<<<<<< HEAD -<<<<<<< HEAD -be an expensive step. If you've got a slice of data to process, be sure to go -over it with .iter() and .iter_mut() if you can, instead of looping by -index. This is Rust and all, so probably you were gonna do that anyway, but just -a heads up.

-======= -======= ->>>>>>> 6b631474faca0645ad16822187c230b813ab6793 be an expensive step. If it's like a 3 element array it's no big deal, but if you've got a big slice of data to process, be sure to go over it with .iter() and .iter_mut() if you can, instead of looping by index. This is Rust and all, so probably you were gonna do that anyway, but just a heads up.

-<<<<<<< HEAD ->>>>>>> object attribute stuff -======= ->>>>>>> 6b631474faca0645ad16822187c230b813ab6793

Get your Tilemap ready

I believe that at one point I alluded to a tilemap existing. Well, just as the tiles are arranged into charblocks, the data describing what tile to show in @@ -372,17 +359,7 @@ separate groups of related registers.

Each of these are a read/write u16 location. This is where we get to all of the important details that we've been putting off.