Copilot proposes asynchronous code, but the target application must use synchronous APIs and cannot add dependencies. Which follow-up is most useful?

Published
  1. Request comments explaining why asynchronous programming is generally useful.
  2. State the synchronous-only and no-new-dependency constraints explicitly, identify the affected functions, and request a revised patch.
  3. Accept the async implementation and document that the application should change later.
  4. Ask Copilot to "try harder" without explaining what was wrong.

Comments — 0