clang-tidy 14.0.6 gives a false-positive bugprone-use-after-move report in chained expressions

[georgthegreat]

Consider the following code

#include <cassert>
#include <vector>

struct test {
 test& foo(std::vector<int> const& v) { assert(v.size() == 1); return *this; }
 int bar(std::vector<int> v ) { return v.size(); }
};

int main() {
    std::vector<int> v = { 42 };
    return test{}.foo(v).bar(std::move(v));

}

clang-tidy 14.0.6 reports the following error:

tidy14-bug/main.cpp:11:23: error: 'v' used after it was moved [bugprone-use-after-move,-warnings-as-errors]
    return test{}.foo(v).bar(std::move(v));
                      ^
tidy14-bug/main.cpp:11:30: note: move occurred here
    return test{}.foo(v).bar(std::move(v));
                             ^
tidy14-bug/main.cpp:11:23: note: the use and move are unsequenced, i.e. there is no guarantee about the order in which they are evaluated
    return test{}.foo(v).bar(std::move(v));
                      ^

The standard, however, clearly defines the behavior for the case.
This false-positive breaks a lot of code in our codebase.

[georgthegreat]

It turns out that the exaple above is broken even with clang-tidy12.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

[EugeneZelenko]

Could you please try 15 or main branch? https://godbolt.org should be helpful.

[georgthegreat]

It would be hard to import entire clang15 toolchain (that is, llvm - clang - clang-tools-extra) into our infrastructure.
Could you, please, point to a commit or a set of commits fixing the problem?

[georgthegreat]

I can not find an option to run clang-tidy via godbolt.
It only supports compilation, and my problem is not related with compilation.

[EugeneZelenko]

Add tool button allow to do this.

[georgthegreat]

clang15 still have this problem:
https://godbolt.org/z/31Prdv1dK

so does clang12

[georgthegreat]

Corresponding StackOverflow discussion is here.

[JonasToth]

the check predates c++17 so very likely the guarantee from c++-17 is not considered in the implementation.

[georgthegreat]

clang-tidy is capable of getting the standard version from cmdline.
This check, however, does not take the standard into account (I am able to reproduce the problem with -std=c++20).