Not sure how this slipped through the cracks, but I'm guessing the build
broke when we upgraded the cpp compilers (to clang 17 and gcc 13).
* Include <cstdint> in a few places
* Suppress -Wstringop-overflow in sparkd-gcc-release build
* Change const char * param to explicit std::string for proper type
deduction in call to 'std::make_tuple'. For some reason, the gcc build
was failing with an array-bounds werror (changing the arg fixed it).
So we can subscribe to depth for "FTX Options" or "FTX BTC Futures",
rather than having to list each security explicitly.
This commit also unhooks binance from MarketDataGateway. A new paradigm
is emerging with the FTX impl, and it'll be easier to redo Binance than
try to make the existing impl fit the new mold.
Unfortunately, ccapi doesn't provide all the security metadata we need, such as
the security type and expiration date/time, so we get the list of FTX
securities directly from the exchange.
This macro defines 2 template specialization fns, 'parse' and 'format'.
* Change 'format' to be a const method
* Declare return type w/ 'decltype' (per latest official example from fmtlib)
Although the build was fine, many methods in this header file depend on 'limits'
so it is appropriate to include it. Presumably all references to such methods are
made from source files that include <limits> by coincidence.
A lot of server-side changes were just merged as part of the Brandon
project (crypto). Many of those changes were in libspark (a lib on
which both the client and server depend), and upgrades to its external
dependencies. As a result, windows counterparts of several upgraded
external libs needed to be similarly upgraded (or added for the first
time). These libs include: boost, btree, catch, curl, fmt, nlohmann json,
openssl, range, rxcpp, websocketpp
This change also makes protobuf generation compatible with python3, and thus
eliminates the build's dependency on python2