Will C++ ever add a thread pool as part of its STL?

[MutantJohn]

It's just, with the advent of std::thread and lambdas, making a thread pool shouldn't be that hard to standardize, right?

I'm not sure how it would be done but couldn't you just create a std::vector<std::thread> threadpool and then construct some number of threads with each thread listening on an unused and unique port? Then couldn't you just pass functions to the container which would then send the data to the appropriate port?

Or is that not how it would work? I'm a super duper network newb but I read that in the most generic sense, a servers and sockets are just inter-process communications so to put a thread in a "wait" state, it should just be listening on a port for incoming data.

Edit :

std::vector<std::thread> pool;
pool.reserve(n);

for (int i = 0; i < n; ++i)
{
    pool.emplace_back([](){
        // begin listening on port blah blah blah
    });
}