Skip to content

Commit e700e6f

Browse files
authored
Update future-functions.md
1 parent f5ed764 commit e700e6f

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/standard-library/future-functions.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,9 @@ In all cases, the associated asynchronous state of the `future` object is not se
5858
5959
The pseudo-function `INVOKE` is defined in [\<functional>](../standard-library/functional.md).
6060
61+
### Microsoft Specific
62+
When the passed function is executed asynchronously, it is executed on Windows Thread Pool. See [Thread Pools](https://docs.microsoft.com/en-us/windows/win32/procthread/thread-pools). Number of concurrent threads is limited to thread pool defaults (currently 500). Number of threads concurrently executing on hardware is currently limited by number of logical processor in the process's processor group. See [Processor Groups](https://docs.microsoft.com/en-us/windows/win32/procthread/processor-groups).
63+
6164
## <a name="future_category"></a> future_category
6265
6366
Returns a reference to the [error_category](../standard-library/error-category-class.md) object that characterizes errors that are associated with `future` objects.

0 commit comments

Comments
 (0)