475a78222f
* XRPLF/pratik/Fix_asan_lsan_flagged_issues: (61 commits) Apply suggestion from @pratikmankawde refactor: Modularize app/tx (6228) do not fix the stack size refactor: Decouple app/tx from `Application` and `Config` (6227) increase timeout chore: Update clang-format to 21.1.8 (6352) reverted change in Number halt on error = 0 remove printXXX from asan rt args remove symbolize option from asan only run asan supp. coro releated asan errors run sanitizer tests in parallel refactor: Modularize `HashRouter`, `Conditions`, and `OrderBookDB` (6226) increase timeout for sanitizer jobs chore: Fix minor issues in comments (6346) refactor: Modularize the NetworkOPs interface (6225) removing timeout changes increase timeout for sanitizer builds, since we are seeing timeouts increase stack size of coroutine ...
protocol
Classes and functions for handling data and values associated with the XRP Ledger protocol.
Serialized Objects
Objects transmitted over the network must be serialized into a canonical format. The prefix "ST" refers to classes that deal with the serialized format.
The term "Tx" or "tx" is an abbreviation for "Transaction", a commonly occurring object type.
Optional Fields
Our serialized fields have some "type magic" to make optional fields easier to read:
- The operation
x[sfFoo]means "return the value of 'Foo' if it exists, or the default value if it doesn't." - The operation
x[~sfFoo]means "return the value of 'Foo' if it exists, or nothing if it doesn't." This usage of the tilde/bitwise NOT operator is not standard outside of therippledcodebase.- As a consequence of this,
x[~sfFoo] = y[~sfFoo]assigns the value of Foo from y to x, including omitting Foo from x if it doesn't exist in y.
- As a consequence of this,
Typically, for things that are guaranteed to exist, you use
x[sfFoo] and avoid having to deal with a container that may
or may not hold a value. For things not guaranteed to exist,
you use x[~sfFoo] because you want such a container. It
avoids having to look something up twice, once just to see if
it exists and a second time to get/set its value.
(Real example)
The source of this "type magic" is in SField.h.