# std::is_copy_assignable, std::is_trivially_copy_assignable, std::is_nothrow_copy_assignable

> C++ Atlas: `cppatlas.com/w/cpp/types/is_copy_assignable` | Source: https://en.cppreference.com/w/cpp/types/is_copy_assignable | Domain: Type support | Standards: C++11, C++14, C++17

If T is not a complete type, (possibly cv-qualified) void, or an array of unknown bound, the behavior is undefined.

## Official Specification Summary (cppreference)

```cpp
// Defined in header <type_traits>

template< class T >
struct is_copy_assignable; // (1) (since C++11)

template< class T >
struct is_trivially_copy_assignable; // (2) (since C++11)

template< class T >
struct is_nothrow_copy_assignable; // (3) (since C++11)
```

| Type trait | The value of the member constant `value` |   |
| --- | --- | --- |
| Type trait | `T` is a referenceable type | `T` is not a referenceable type |
| (1) | `std::is_assignable<T&, const T&>::value` | `false` |
| (2) | `std::is_trivially_assignable<T&, const T&>::value` | `false` |
| (3) | `std::is_nothrow_assignable<T&, const T&>::value` | `false` |

If `T` is not a complete type, (possibly cv-qualified) `void`, or an array of unknown bound, the behavior is undefined.

If an instantiation of a template above depends, directly or indirectly, on an incomplete type, and that instantiation could yield a different result if that type were hypothetically completed, the behavior is undefined.

If the program adds specializations for any of the templates described on this page, the behavior is undefined.

#### Helper variable templates

```cpp
template< class T >
inline constexpr bool is_copy_assignable_v =
    is_copy_assignable<T>::value; // (since C++17)

template< class T >
inline constexpr bool is_trivially_copy_assignable_v =
    is_trivially_copy_assignable<T>::value; // (since C++17)

template< class T >
inline constexpr bool is_nothrow_copy_assignable_v =
    is_nothrow_copy_assignable<T>::value; // (since C++17)
```

### Inherited from std::integral_constant

#### Member constants

- `value` [static]: `true` if `T` is copy-assignable, `false` otherwise (public static member constant)

#### Member functions

- `operator bool`: converts the object to `bool`, returns `value` (public member function)
- `operator()` (C++14): returns `value` (public member function)

#### Member types

**Type — Definition**

- `value_type`: `bool`
- `type`: `std::integral_constant<bool, value>`

#### Possible implementation

```cpp
template<class T>
struct is_copy_assignable
    : std::is_assignable<typename std::add_lvalue_reference<T>::type,
                         typename std::add_lvalue_reference<const T>::type> {};

template<class T>
struct is_trivially_copy_assignable
    : std::is_trivially_assignable<typename std::add_lvalue_reference<T>::type,
                                   typename std::add_lvalue_reference<const T>::type> {};

template<class T>
struct is_nothrow_copy_assignable
    : std::is_nothrow_assignable<typename std::add_lvalue_reference<T>::type,
                                 typename std::add_lvalue_reference<const T>::type> {};
```

#### Notes

The trait `std::is_copy_assignable` is less strict than *CopyAssignable* because it does not check the type of the result of the assignment (which, for a *CopyAssignable* type, must be an lvalue of type `T`) and does not check the semantic requirement that the argument expression remains unchanged. It also does not check that `T` satisfies *MoveAssignable*, which is required of all *CopyAssignable* types.

#### Example

```cpp
#include <iostream>
#include <type_traits>
#include <utility>

struct Foo { int n; };

int main()
{
    std::cout << std::boolalpha
              << "Foo is trivially copy-assignable? "
              << std::is_trivially_copy_assignable<Foo>::value << '\n'
              << "int[2] is copy-assignable? "
              << std::is_copy_assignable<int[2]>::value << '\n'
              << "int is nothrow copy-assignable? "
              << std::is_nothrow_copy_assignable<int>::value << '\n';
}
```

Output:

```text
Foo is trivially copy-assignable? true
int[2] is copy-assignable? false
int is nothrow copy-assignable? true
```

#### Defect reports

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

| DR | Applied to | Behavior as published | Correct behavior |
| --- | --- | --- | --- |
| LWG 2196 | C++11 | the behavior was unclear if `const T&` cannot be formed | the value produced is `false` in this case |

#### See also

- [`is_assignable`](https://en.cppreference.com/w/cpp/types/is_assignable) (C++11), [`is_trivially_assignable`](https://en.cppreference.com/w/cpp/types/is_assignable) (C++11), [`is_nothrow_assignable`](https://en.cppreference.com/w/cpp/types/is_assignable) (C++11): checks if a type has an assignment operator for a specific argument (class template)
- [`is_move_assignable`](https://en.cppreference.com/w/cpp/types/is_move_assignable) (C++11), [`is_trivially_move_assignable`](https://en.cppreference.com/w/cpp/types/is_move_assignable) (C++11), [`is_nothrow_move_assignable`](https://en.cppreference.com/w/cpp/types/is_move_assignable) (C++11): checks if a type has a move assignment operator (class template)

---
Attribution: content from https://en.cppreference.com/w/cpp/types/is_copy_assignable (cppreference.com), licensed under CC-BY-SA 3.0 and GFDL. Modified: converted to markdown, study notes added. Offline snapshot of 9 February 2025.