Looks like we'll actually retain and use this low-level solution in cases where we just can not afford heap allocations but need to keep polymorphic objects close to one another in memory. Since single linked lists are filled by prepending, it is rather common to need the reversed order of elements for traversal, which can be achieved in linear time. And while we're here, we can modernise the templated emplacement functions |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||