4 ms·
People have dealt with the audience question. As for the “non-sequitur” comment, as someone who has read similar material for other allocators, I can attest tha
by cormacrelf 4y ago
People have dealt with the audience question. As for the “non-sequitur” comment, as someone who has read similar material for other allocators, I can attest that every paragraph was in exactly the order it needed to be to understand the allocator design pretty quickly. It was actually really well structured. Allocators are hard to understand, not least because there are so many synonyms for both “some quantity of contiguous memory” and “collections of various types of those”. This piece came armed with diagrams, code examples that expose what’s happening behind the scenes, and walkthroughs of typical allocator executions at a very appropriate level of detail: enough to appreciate why it might work quite well. It didn’t compare to other designs but it was a worthy contribution of knowledge on its own.
(Edit, oh look at that, previously bookmarked 7 years ago.)
- saagarjha 4y ago+1 this basically matches how a typical guide to an allocator is structured. As such it assumes basic familiarity with how theses things work.