[Lldb-commits] [lldb] [llvm] [mlir] Split the llvm::ThreadPool into an abstract base class and an implementation (PR #82094)

[Georgios Pinitas via lldb-commits]

================
@@ -227,7 +265,7 @@ class ThreadPool {
 class ThreadPoolTaskGroup {
----------------
GeorgeARM wrote:

Sure you can convert the address of the object to a string or int that is fine; it is not the best but not worse than what is there. You can do this inside the `ThreadPoolTaskGroup` which is essentially a RAII wrapper.
What you get is probably a cleaner API IMHO and don't impose to the implementations to have to consume a struct that by definition loops around the interface. 

https://github.com/llvm/llvm-project/pull/82094