Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 28
    The answer is as simple as this IMO. The difference between a synchronous and asynchronous process isn't an implementation detail - it's a semantically different contract. Commented Dec 5, 2018 at 17:33
  • 11
    @AntP: I disagree that it's that simple; it surfaces in the C# language, but not in the Go language for example. So this is not an inherent property of asynchronous processes, it's a matter of how asynchronous processes are modeled in the given language. Commented Dec 6, 2018 at 9:39
  • 1
    @MatthieuM. Yes, but you can use async methods in C# to provide synchronous contracts too, if you want to. The only difference is that Go is asynchronous by default while C# is synchronous by default. async gives you the second programming model - async is the abstraction (what it actually does depends on runtime, task scheduler, synchronization context, awaiter implementation...). Commented Dec 9, 2018 at 7:33