> providing both sync and async code paths in the same class, often using a naming scheme which prefixes the async versions of the methods with an a
I have a solution to write a single code path for both async and sync
https://news.ycombinator.com/item?id=43982570
I don't really understand what that does.
I don't really understand what that does.