Return value of thrust::minmax_element differs from STL's minmax_element

In both STL and thrust a call to `minmax_element` returns a pair of iterators, the first points to the minimum and the second to the maximum value. In both STL and thrust, if more than run minimum exists, the first value is chosen. If more than one maximum value exists, the STL version chooses the last candidate while thrust chooses the first one. While I think the STL is quite inconsistent here, I'd still prefer if thrust would behave just like the STL

Best wishes,
maribu