* XRPLF/develop: (81 commits) ci: Only publish docs in public repos (6687) chore: Enable remaining clang-tidy `performance` checks (6648) refactor: Address PR comments after the modularisation PRs (6389) chore: Fix clang-tidy header filter (6686) ci: [DEPENDABOT] bump actions/deploy-pages from 4.0.5 to 5.0.0 (6684) ci: [DEPENDABOT] bump codecov/codecov-action from 5.5.3 to 6.0.0 (6685) fix: Guard Coro::resume() against completed coroutines (6608) refactor: Split LoanInvariant into LoanBrokerInvariant and LoanInvariant (6674) ci: Don't publish docs on release branches (6673) refactor: Make function naming in ServiceRegistry consistent (6390) chore: Shorten job names to stay within Linux 15-char thread limit (6669) fix: Improve loan invariant message (6668) ci: Upload artifacts only in public repositories (6670) ci: Add conflicting-pr workflow (6656) chore: Add more AI tools to .gitignore (6658) chore: Show warning message if user may need to connect to VPN (6619) feat: Add placeholder amendment for assorted bug fixes (6652) chore: Update sqlite3->3.51.0, protobuf->6.33.5, openssl->3.6.1, grpc->1.78.1 (6653) refactor: Modularise ledger (6536) chore: Use unpatched version of soci (6649) ...
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.