[PATCH] D114183: [ThreadPool] Add template argument for future result type.

[Mehdi AMINI via Phabricator via llvm-commits]

mehdi_amini added a comment.

This seems like a bit of a "niche" extension: it makes it possible to return future but only for a statically predefined type. Is there a way to type-erase this in the threadpool a bit better and manager this at "enqueue time" instead so that each new task can return its own future?

Also isn't this feature something that can likely be layered on top of the existing ThreadPool without changing it? 
For example by wrapping the submitted task into another object that manages the promise/future.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D114183/new/

https://reviews.llvm.org/D114183