Open clarksmr opened 5 months ago
It would go here, after Red-Black Trees?
I was wondering during class if in order for amortized $\mathcal{O}(1)$ cost per read operation there needs to be habitual copying of the array when version tree paths get "too long" or duplicate updates are performed? Or does rebasing handle that already (because it doesn't seem to resolve the issue that update paths can grow long)?
A new section in Chapter 8 should be added about persistent arrays, which are now covered in lecture.