lumiera_documentation/tests/vault/mem
Ichthyostega 8d563d1ea9 BufferProvider: lift the family-ID to the BufferStage level
During the last days, I started with analysis to find a way
to operate the `BufferProvider`, as implemented thus far,
within a massively concurrent environment.

Since I intend to create thread-local caches,
the initialisation of the `BufferMetadata` store must be static.

It turns out that the root-ID, which acts like a mandator ID,
is only used at a single code path, when creating or accessing
an abstract type-Key. It is thus easy to extract and relocate
this distinguishing ID into the actual `BufferStage` implementation.
2026-04-17 19:08:46 +02:00
..
buffer-metadata-key-test.cpp BufferProvider: relocate into Vault Layer 2026-03-08 00:53:41 +01:00
buffer-metadata-test.cpp BufferProvider: lift the family-ID to the BufferStage level 2026-04-17 19:08:46 +02:00
buffer-provider-protocol-test.cpp BufferProvider: relocate into Vault Layer 2026-03-08 00:53:41 +01:00
buffer-proxy-adaptor-test.cpp OutputSlot: consider how to integrate the proxy provider 2026-03-17 00:48:08 +01:00
buffer-store-test.cpp BufferProvider: complete the clean-up effort 2026-04-14 01:22:55 +02:00
diagnostic-buffer-provider-test.cpp BufferProvider: relocate into Vault Layer 2026-03-08 00:53:41 +01:00
extent-family-test.cpp Tests: build an link a test-support library 2026-03-06 23:16:32 +01:00