Unifying the many ways to compare

Date: 2018-10-07
Author: David Stone (davidmstone@google.com, david@doublewise.net)
Audience: Library Evolution Working Group (LEWG)



We currently have several facilities to compare things (mostly strings). We should unify on "the one true way". For reference, the currently existing functionality relevant to this paper (other than existing comparison operators) is:

Note that for char_traits, we also have a "character traits" 'concept' with the same requirements as the concrete char_traits type.