`bugprone-use-after-move` not reported for usage after `std::move()` with range

[firewave]

#include <algorithm>
#include <iostream>
#include <iterator>
#include <list>
#include <string>

int main()
{
    std::list<std::string> l1 = { "1" };

    std::list<std::string> l2;
    std::move(l1.begin(), l1.end(), std::back_inserter(l2));

    std::cout << "l1: " << *l1.cbegin() << '\n';
    std::cout << "l2: " << *l2.cbegin() << '\n';
}

https://godbolt.org/z/Y96a6nv7h

https://en.cppreference.com/w/cpp/algorithm/move

Also not detected by the Clang Static Analyzer clang-analyzer-cplusplus.Move check: #137157.

[llvmbot]

@llvm/issue-subscribers-clang-tidy

Author: Oliver Stöneberg (firewave)

``` #include <algorithm> #include <iostream> #include <iterator> #include <list> #include <string>

int main()
{
std::list<std::string> l1 = { "1" };

std::list<std::string> l2;
std::move(l1.begin(), l1.end(), std::back_inserter(l2));

std::cout << "l1: " << *l1.cbegin() << '\n';
std::cout << "l2: " << *l2.cbegin() << '\n';

}

https://godbolt.org/z/Y96a6nv7h

https://en.cppreference.com/w/cpp/algorithm/move
</details>

[vbvictor]

In docs it says

The check currently only considers calls of std::move on local variables or function parameters. It does not check moves of member variables or global variables.

So for now it doesn't consider std::move from algorithm by design. Maybe we should remove false-negative tag and add enhancement?

[firewave]

In docs it says

The check currently only considers calls of std::move on local variables or function parameters. It does not check moves of member variables or global variables.

Neither of the variables in my example are members or global.

So for now it doesn't consider std::move from algorithm by design. Maybe we should remove false-negative tag and add enhancement?

Fair enough.