No description
Find a file
Folling 521c61c8fb
update sqlitecpp
Signed-off-by: Folling <mail@folling.io>
2025-01-01 14:07:46 +01:00
docs a new beginning 2025-01-01 14:07:46 +01:00
include restructure into smaller files & add IWYU/clang-tidy 2025-01-01 14:07:46 +01:00
src restructure into smaller files & add IWYU/clang-tidy 2025-01-01 14:07:46 +01:00
vendor update sqlitecpp 2025-01-01 14:07:46 +01:00
.clang-format restructure into smaller files & add IWYU/clang-tidy 2025-01-01 14:07:46 +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 restructure into smaller files & add IWYU/clang-tidy 2025-01-01 14:07:46 +01:00
implementation_details a new beginning 2025-01-01 14:07:46 +01:00
LICENSE.md add license 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.