Async feedback: overloads that differ only in async

[Douglas_Gregor]

@gwendal.roue

Now I think I can directly call @John_McCall and @Douglas_Gregor. There exists a workaround to the overloads that differ only in async limitation. So people will use it. I plan to use it. Would you consider removing the limitation, so that we are not forced to use this ugly workaround?

I think it's worth considering, yes, and we've noted before that we'll certainly consider amending proposals as more usage experience comes in. XCTest has a similar issue where there are very good reasons to need to overload async and non-async (the pre-async version has the good name and needs to stick around). Would you be willing to write up an amendment to SE-0296, along the lines of what we did to amend SE-0306 for better nonisolated let semantics, and a member of the Core Team will run a review for it next week?

Doug