# Talk:cpp/algorithm/equal

##  Simplification of possible implementation

While I appreciate brevity, I'm inclined to think that defining the possible implementation in terms of mismatch is less useful than what we had before. The previous version had two things going for it: it wasn't very long itself, and it allowed you to see how equal might work without requiring an understanding of how mismatch works.

I can understand explaining something in terms of something else if it makes the explanation much more clear, but I don't think that's really the case here. Any thoughts about this (Newacct or others?) --Nate (talk) 07:37, 10 October 2013 (PDT)

I think expressed in terms of mismatch it becomes conceptually more complex: building a pair of iterators and then only using one. But I didn't see any requirements violations, so it is, technically, a possible implementation. --Cubbi (talk) 09:27, 10 October 2013 (PDT)