Since the BufferStore implementation component is now supposed to handle only the memory allocation, a complete end-to end data flow must be ensured, so that allocation / deallocation functions get all the relevant information. Notably, the `LocalTag` is now used as an implementation-defined conduit for further (opaque) marker data. Since all data passed over this API are simple values (even `LocalTag` is effectively a 64bit integer), we can now avoid relying on output parameters or similar side-effect tricks. |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||