std::promise::set_value_at_thread_exit - cppreference.com

##### cppreference.com

##### Search

Create account

##### Namespaces

- Page
- Discussion

##### Variants

##### Views

- View
- Edit
- History

##### Actions

# std::promise::set_value_at_thread_exit

From cppreference.com
< cpp‎ | thread‎ | promise

void set_value_at_thread_exit( const R& value ); | (1) | (member only of generic `promise` template) (since C++11)
void set_value_at_thread_exit( R&& value ); | (2) | (member only of generic `promise` template) (since C++11)
void set_value_at_thread_exit( R& value ); | (3) | (member only of `promise<R&>` template specialization) (since C++11)
void set_value_at_thread_exit() | (4) | (member only of `promise<void>` template specialization) (since C++11)

Stores the `value` into the shared state without making the state ready immediately. The state is made ready when the current thread exits, after all variables with thread-local storage duration have been destroyed.

The operation is atomic, i.e. it behaves as though they acquire a single mutex associated with the promise object while updating the promise object.

An exception is thrown if there is no shared state or the shared state already stores a value or exception.

### [edit] Parameters

value | - | value to store in the shared state

### [edit] Return value

(none)

### [edit] Exceptions

std::future_error on the following conditions:

- *this has no shared state. The error category is set to `no_state`.

- The shared state already stores a value or exception. The error category is set to `promise_already_satisfied`.

Additionally:

1-2) Any exception thrown by the copy constructor of `value`
3) Any exception thrown by the move constructor of `value`

### [edit] Example

| This section is incomplete Reason: no example

### [edit] See also

set_value | sets the result to specific value (public member function) [edit]

Retrieved from "http://en.cppreference.com/mwiki/index.php?title=cpp/thread/promise/set_value_at_thread_exit&oldid=59220"
Category:

- Todo no example