Add a list of issues to solve before v1.0

[BraINstinct0]

It's been over 5 years since the last release, and many promising enhancements were mentioned in this repo.
And still no v1.0.0 release.
To get a clearer view of the issues standing in the path to release (and possibly get some PRs that'll solve some), listing them (either exhaustively/not-so) in the Readme would be helpful.

[ariccio]

The real blocking issue is that the clever hacky mechanism I'd used to parallelize all those individual directory walking calls, std::async, used to be implemented incorrectly, but better by Microsoft in VS2013. They were using the Concurrency Runtime to dispatch std::async calls on the threadpool, which really really nicely works like magic. But apparently, the standard says each call is supposed to launch a new thread, which does not work at ALL. It's not even slow, it just hangs the whole app once it gets to 700 threads or so. I've experimented with using the excellent windows threadpool, but for some reason, it doesn't seem to like dispatching new tasks from within tasks already running on the threadpool.

If it was clear to me how I wanted the async/parallel mechanism to work, I could say pretty clearly what needed to be done! But I have no clue yet... and it would be cruel to subject anybody to the uglyness that is the core directory walking code before then :)

[ariccio]

Other than that, I'm wasting a lot of time being OCD about MFC. I hate the way that MFC works in general, and am probably wasting my time here, but I want to refactor a lot of code away from MFC. I love WTL so far, even though they don't always check return codes enough. OCD is a curse :D

[WarlockD]

That sums up my thoughts on this. Spent better part of 10 min waiting for the old windat to work to look up to see if there is chnage, see your changes and thing "Oh this is better" But now thatI figured out the file issue, its like done. Thanks for your work, even if it is thankless:P

[WarlockD]

Oh god. I am running the expermental branch of C+22, how the fuck are coroutines being run

[ariccio]

Heh, last I played with coroutines in C++ on MSVC, they were using some insane black magic behind the scenes... and yet they were still to opaque for me to really understand! It was (is?) kinda a mysterious interface because it's deliberately minimal and unopinionated.