Don't export `results`?

[IanButterworth]

I typically use using and was surprised to see that ThreadPools exports results which is a very generic name to export.

Just a suggestion, but perhaps if that needs to be exported, it could have a less generic name?

[tro3]

Actually, that just looks like a cut & paste issue or something. Zero reason to export that. I will fix.

[tro3]

Oh, that is an actual function. You're right - it is too generic - changing it to poolresults will be API-breaking. But so be it.

[IanButterworth]

Thanks!

[tro3]

Rev 2.0.0 is making its way through the system