No description
Find a file
Folling 5da995b47e
make object fields public and fixup compile errors
Signed-off-by: Folling <mail@folling.io>
2025-01-01 14:07:47 +01:00
docs finalise interface & documentation 2025-01-01 14:07:46 +01:00
include make object fields public and fixup compile errors 2025-01-01 14:07:47 +01:00
src make object fields public and fixup compile errors 2025-01-01 14:07:47 +01:00
vendor adjust values api to vector-esque interface 2025-01-01 14:07:47 +01:00
.clang-format make values capable of being a list & add boost 2025-01-01 14:07:47 +01:00
.clang-tidy make object fields public and fixup compile errors 2025-01-01 14:07:47 +01:00
.gitignore a new beginning 2025-01-01 14:07:46 +01:00
.gitmodules a new beginning 2025-01-01 14:07:46 +01:00
CMakeLists.txt make values capable of being a list & add boost 2025-01-01 14:07:47 +01:00
LICENSE.md finalise interface & documentation 2025-01-01 14:07:46 +01:00
README.md a new beginning 2025-01-01 14:07:46 +01:00

Data Longevity

All data returned by libikarus is ephemeral and only represents the state of the project at the time of the request. A snapshot if you will. One must not rely on it representing the actual state of the project at any given time. The data is simply copied from the underlying data sources and returned to the caller.

No mechanisms are provided to avoid race conditions. LibIkarus itself should only be used in a single-threaded context. However, nothing breaks if you do use it in a multithreaded context, that is, libikarus is threadsafe. You just cannot rely on the data being consistent. This goes especially for inter-process access to the same project.