It’s a dynamically-sized list of objects of the same type stored contiguously in memory.
dynamically-sized: The size of it can change as needed.
list: It stores multiple things together.
object: A bit of programmer defined data.
of the same type: all the objects in the list are defined the same way
stored contigiously in memory: if you think of memory as a bookshelf then all the objects on the list would be stored right next to each other on the bookshelf rather than spread across the bookshelf.
Dynamically sized but stored contiguously makes the systems performance engineer in me weep. If the lists get big, the kernel is going to do so much churn.
matlab likes to pick the smallest available spot in memory to store a list, so for loops that increase the size of a matrix it’s recommended to preallocate the space using a matrix full of zeros!
dynamically-sized: The size of it can change as needed.
list: It stores multiple things together.
object: A bit of programmer defined data.
of the same type: all the objects in the list are defined the same way
stored contigiously in memory: if you think of memory as a bookshelf then all the objects on the list would be stored right next to each other on the bookshelf rather than spread across the bookshelf.
Dynamically sized but stored contiguously makes the systems performance engineer in me weep. If the lists get big, the kernel is going to do so much churn.
Is that churn or chum? (RN or M)
Churm
matlab likes to pick the smallest available spot in memory to store a list, so for loops that increase the size of a matrix it’s recommended to preallocate the space using a matrix full of zeros!