[libc++][NFC] Don't rely on `<algorithm>` transitively including `<memory>` in tests

[fsb4000]

Summary

Found by @cpplearner (https://github.com/microsoft/STL/pull/2976#discussion_r935440806)

[Mordante]

Thanks, LGTM!

[var-const]

@fsb4000 Thank you for the patch! Would you mind to update the description to something like the following?

[libc++][NFC] Don't rely on `<algorithm>` transitively including `<memory>` in tests

(The current description identifies the problem; I think it would be clearer to describe the fix instead)

libcxx/test/std/algorithms/ranges_result_alias_declarations.compile.pass.cpp

17

In libc++, <algorithm> transitively includes <memory>, which must be why we never noticed.

[fsb4000]

Would you mind to update the description to something like the following?

Sure.
Done.

[var-const]

LGTM, thanks!

libcxx/test/std/algorithms/ranges_result_alias_declarations.compile.pass.cpp

 //===----------------------------------------------------------------------===//
 //
 // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
 // See https://llvm.org/LICENSE.txt for license information.
 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
 //
 //===----------------------------------------------------------------------===//
 
 // UNSUPPORTED: c++03, c++11, c++14, c++17
 // UNSUPPORTED: libcpp-has-no-incomplete-ranges
 
 // <algorithm>
 
 // ensure that all result alias declarations are defined
 
 #include <algorithm>
+#include <memory>
 #include <type_traits>
 
 using namespace std::ranges;
 
 static_assert(std::is_same_v<in_fun_result<int, long>, for_each_result<int, long>>);
 static_assert(std::is_same_v<in_fun_result<int, long>, for_each_n_result<int, long>>);
 
 static_assert(std::is_same_v<in_in_result<int, long>, mismatch_result<int, long>>);