On 16.12.19 23:19, Zach Laine via Boost wrote:
- operators < and == can be provided, since the requirements of these
functions already suggest a default implementation. The user can still override the provided implementation if a more efficient implementation is possible. If it is for some reason desirable to create a container without operator <, an additional policy argument could be added to container_interface.
These are all provided; I think you just missed them.
operator== is listed in Table 1.3, and in the User-Defined column of Table 1.4. The note in Table 1.8 also says that operator== is required to be user-defined. So if the library provides it, then the documentation does not reflect this. -- Rainer Deyke (rainerd@eldwood.com)