Skip to main content
edited body
Source Link
Ginger
  • 2.7k
  • 1
  • 9
  • 46

In a lot of modern languages (such as Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so isare there a way to avoid itany alternatives?

In a lot of modern languages (such as Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so is there a way to avoid it?

In a lot of modern languages (such as Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so are there any alternatives?

deleted 2 characters in body
Source Link
Ginger
  • 2.7k
  • 1
  • 9
  • 46

In a lot of modern languages (primarilysuch as Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so is there a way to avoid it?

In a lot of modern languages (primarily Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so is there a way to avoid it?

In a lot of modern languages (such as Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so is there a way to avoid it?

Source Link
Ginger
  • 2.7k
  • 1
  • 9
  • 46

Must async functions always be marked as such?

In a lot of modern languages (primarily Python), asynchronous functions (those that return coroutines) must be explicitly marked as such:

async function foo():
    pass

Is there any specific reason for this, and if so is there a way to avoid it?