introduce OrderMatcher optional parameter for TradingPool and HistoryPool constructors.
These changes don't violate current API and allow to reduce boilerplate code in case of defining TradingPool and HistoryPool since matching criteria for both are often identical. It can also be useful when defining pools as RAII objects. For example:
Changes:
OrderPool
to interface;OrderPoolMatcher
class;OrderMatcher
optional parameter forTradingPool
andHistoryPool
constructors.These changes don't violate current API and allow to reduce boilerplate code in case of defining
TradingPool
andHistoryPool
since matching criteria for both are often identical. It can also be useful when defining pools as RAII objects. For example: