std::list::unique(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

🌸 NAME 🌸

okay so bestie, this is std::list::unique β€” as in std::list::unique(3) β€” from the C++ Standard Library, and it is literally the β€œconsecutive dupes? not on my watch” member function. It removes all consecutive duplicate elements from the container. Only the first element in each group of equal elements is left. And the important tea: it invalidates only the iterators and references to the removed elements. πŸ’…


✨ SYNOPSIS ✨

void unique();                                 (until C++20)
size_type unique();                            (since C++20)
template< class BinaryPredicate >      (1)                   (until C++20)
void unique( BinaryPredicate p );          (2)
template< class BinaryPredicate >                            (since C++20)
size_type unique( BinaryPredicate p );

So basically:

  1. Uses operator== to compare the elements.
  2. Uses p to compare the elements.
⚠️ Undefined behavior alert, no cap: the behavior is undefined if the corresponding comparator does not establish an equivalence relation. That is not a vibe you want.

πŸŽ€ PARAMETERS πŸŽ€

  • p β€” a binary predicate which returns true if the elements should be treated as equal.

The signature of the predicate function should be equivalent to the following:

bool pred(const Type1 &a, const Type2 &b);

While the signature does not need to have const &, the function must not modify the objects passed to it and must be able to accept all values of type (possibly const) Type1 and Type2 regardless of value category. Thus, Type1 & is not allowed, nor is Type1 unless for Type1 a move is equivalent to a copy (since C++11). The types Type1 and Type2 must be such that an object of type list<T,Allocator>::const_iterator can be dereferenced and then implicitly converted to both of them. 🫢


πŸ¦‹ TYPE REQUIREMENTS πŸ¦‹

  • BinaryPredicate must meet the requirements of BinaryPredicate.

πŸ’– RETURN VALUE πŸ’–

  • (none) β€” until C++20.
  • The number of elements removed. β€” since C++20.

πŸ”₯ COMPLEXITY πŸ”₯

If empty() is true, no comparison is performed.

Otherwise, given N as std::distance(begin(), end()):

  1. Exactly N-1 comparisons using operator==.
  2. Exactly N-1 applications of the predicate p.

🌈 NOTES 🌈

Feature-test macro moment:

  • __cpp_lib_list_remove_return_type β€” value 201806L, standard (C++20), feature: β€œChange the return type”.

πŸ§ͺ EXAMPLE πŸ§ͺ

Run this code, bestie β€” it’s giving main character energy:

#include <iostream>
#include <list>

std::ostream& operator<< (std::ostream& os, std::list<int> const& container)
{
    for (int val : container)
        os << val << ' ';
    return os << '\n';
}

int main()
{
    std::list<int> c{1, 2, 2, 3, 3, 2, 1, 1, 2};
    std::cout << "Before unique(): " << c;
    const auto count1 = c.unique();
    std::cout << "After unique():  " << c
              << count1 << " elements were removed\n";

    c = {1, 2, 12, 23, 3, 2, 51, 1, 2, 2};
    std::cout << "\nBefore unique(pred): " << c;

    const auto count2 = c.unique([mod = 10](int x, int y)
    {
        return (x % mod) == (y % mod);
    });

    std::cout << "After unique(pred):  " << c
              << count2 << " elements were removed\n";
}

Output πŸ’…

Before unique(): 1 2 2 3 3 2 1 1 2
After unique():  1 2 3 2 1 2
3 elements were removed

Before unique(pred): 1 2 12 23 3 2 51 1 2 2
After unique(pred):  1 2 23 2 51 2
4 elements were removed

🩹 DEFECT REPORTS 🩹

The following behavior-changing defect reports were applied retroactively to previously published C++ standards.

  • LWG 1207 β€” applied to C++98. Behavior as published: it was unclear whether iterators and/or references will be invalidated. Correct behavior: only invalidates iterators and references to the removed elements.

πŸ‘‘ SEE ALSO πŸ‘‘

  • unique β€” removes consecutive duplicate elements in a range (function template).

mwah πŸ’‹ this page is sourced from http://cppreference.com, dated 2024.06.10, and yeah bestie, it’s still std::list::unique(3) β€” periodt. 🌟

πŸ“¦ where this page comes from