Brilliant. Interface/contract-based programming makes implementation much easier on on newcomers, which is something I think the could improve on. Consider me an adopter.
@7:40 For your comparison operators = , is there a good reason to also call operator== ? I would think its more efficient to just logical negate the "opposite" operation, so only operator< is required for those. Like this (hopefully youtube comment doesn't mangle code paste here): operator() { return rhs < lhs; } operator rhs); } operator>=() { return !(lhs < rhs); }
Brilliant. Interface/contract-based programming makes implementation much easier on on newcomers, which is something I think the could improve on. Consider me an adopter.
@7:40 For your comparison operators = , is there a good reason to also call operator== ? I would think its more efficient to just logical negate the "opposite" operation, so only operator< is required for those. Like this (hopefully youtube comment doesn't mangle code paste here):
operator() { return rhs < lhs; }
operator rhs); }
operator>=() { return !(lhs < rhs); }