Reply to thread

Message: [QUOTE="Juha Nieminen, post: 3809219"] I know that the iterator template parameter and the value template parameter are not forced to be related to the same type, and that because of how a function like std::equal_range has been implemented, it compiles and works like a marvel. However, does the C++ standard guarantee that an algorithm like std::equal_range must always work correctly even if the iterators and the value (and thus also the comparator) refer to completely unrelated types, as long as the comparator has been implemented properly to accept these two different types? Why does MSVC++ complain about this when enough concept checks have been turned on? Is it a compiler bug? [/QUOTE]