mirror of
https://github.com/XRPLF/rippled.git
synced 2026-04-29 15:37:57 +00:00
02c9830184
- Add Doxygen documentation to new methods, members, constants, and macros introduced by the TSAN/ASAN PR (Database::startReadThreads, BasicApp::DeferStart, ResourceManager::start, XRPL_SANITIZER_ACTIVE, coroStackSize, yieldStackSize) - Add @note thread-safety tags where atomics were introduced - Update Database constructor docs to reflect deferred thread startup - Remove temporary CI filter that restricted builds to sanitizer-only variants (must run full matrix before merge) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Basics
Utility functions and classes.
ripple/basic should contain no dependencies on other modules.
Choosing a rippled container.
-
std::vector- For ordered containers with most insertions or erases at the end.
-
std::deque- For ordered containers with most insertions or erases at the start or end.
-
std::list- For ordered containers with inserts and erases to the middle.
- For containers with iterators stable over insert and erase.
- Generally slower and bigger than
std::vectororstd::dequeexcept for those cases.
-
std::set- For sorted containers.
-
xrpl::hash_set- Where inserts and contains need to be O(1).
- For "small" sets,
std::setmight be faster and smaller.
-
xrpl::hardened_hash_set- For data sets where the key could be manipulated by an attacker in an attempt to mount an algorithmic complexity attack: see http://en.wikipedia.org/wiki/Algorithmic_complexity_attack
The following container is deprecated
std::unordered_set- Use
xrpl::hash_setinstead, which uses a better hashing algorithm. - Or use
xrpl::hardened_hash_setto prevent algorithmic complexity attacks.