Timeline for Aren't the guidelines of async/await usage in C# contradicting the concepts of good architecture and abstraction layering?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2018 at 15:45 | audit | First posts | |||
| Dec 14, 2018 at 0:24 | |||||
| Dec 9, 2018 at 7:33 | comment | added | Luaan | @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...). | |
| Dec 6, 2018 at 9:39 | comment | added | Matthieu M. | @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. | |
| Dec 5, 2018 at 17:33 | comment | added | Ant P | 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. | |
| Dec 5, 2018 at 10:29 | history | edited | max630 | CC BY-SA 4.0 | added 1 character in body |
| Dec 5, 2018 at 9:58 | history | answered | max630 | CC BY-SA 4.0 |