# Inconsistent behaviour of argmax

**URL:** <https://discourse.julialang.org/t/inconsistent-behaviour-of-argmax/134373>\
**Category:** General Usage\
**Created:** [December 5, 2025, 9:57am UTC](https://discourse.julialang.org/t/inconsistent-behaviour-of-argmax/134373 "2025-12-05T09:57:38Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [December 5, 2025, 12:10pm UTC](https://discourse.julialang.org/t/inconsistent-behaviour-of-argmax/134373/3 "2025-12-05T12:10:25Z")

</div>

> [@\`findmax\` and friends: confusing behaviour to be introduced in 1.7](https://discourse.julialang.org/t/findmax-and-friends-confusing-behaviour-to-be-introduced-in-1-7/61904):
>
> Several people, including myself, have tried to raise this issue during last months. There were multiple posts on slack, and even a GH issue ([https://github.com/JuliaLang/julia/issues/39203](https://github.com/JuliaLang/julia/issues/39203)). I’ll try to raise it once more, here on discourse, hoping that it gets more traction. The findmax(A) function, which everyone is used to, returns the maximum value in the array A and its index. However, Julia 1.7 will introduce a findmax(f, A) version, that doesn’t return any index at all: julia\> A = [5, …

---

_[View the full topic](https://discourse.julialang.org/t/inconsistent-behaviour-of-argmax/134373)._
