No description
Find a file
folling ee85c53354
remove logging statements
Signed-off-by: Folling <mail@folling.io>
2025-04-15 12:10:48 +02:00
docs finalise interface & documentation 2025-04-15 12:10:38 +02:00
include change clang-format 2025-04-15 12:10:47 +02:00
src remove logging statements 2025-04-15 12:10:48 +02:00
vendor remove logging statements 2025-04-15 12:10:48 +02:00
.clang-format change clang-format 2025-04-15 12:10:47 +02:00
.clang-tidy make object fields public and fixup compile errors 2025-04-15 12:10:46 +02:00
.gitignore a new beginning 2025-04-15 12:10:33 +02:00
.gitmodules a new beginning 2025-04-15 12:10:33 +02:00
clang-format.txt remove logging statements 2025-04-15 12:10:48 +02:00
CMakeLists.txt make values capable of being a list & add boost 2025-04-15 12:10:43 +02:00
LICENSE.md finalise interface & documentation 2025-04-15 12:10:38 +02:00
README.md a new beginning 2025-04-15 12:10:33 +02: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.