Asynchronous programming is in demand today, because responsiveness is increasingly important on all modern devices. Yet, we know little about how developers use asynchronous programming in practice. Without such knowledge, developers, researchers, language and library designers, and tool providers can make wrong assumptions. We present the first study that analyzes the usage of asynchronous programming in a large experiment. We analyzed 1378 open source Windows Phone (WP) apps, comprising 12M SLOC, produced by 3376 developers. Using this data, we answer 2 research questions about use and misuse of asynchronous constructs. Inspired by these findings, we developed (i) Asyncifier, an automated refactoring tool that converts callback-based asynchronous code to use async/await; (ii) Corrector, a tool that finds and corrects common misuses of async/await. Our empirical evaluation shows that these tools are (i) applicable and (ii) efficient. Developers accepted 314 patches generated by our tools.
|Title of host publication||ICSE 2014 Proceedings of the 36th International Conference on Software Engineering|
|Publisher||Association for Computing Machinery (ACM)|
|Pages||1117 - 1127|
|Publication status||Published - 2014|
Okur, S., Hartveld, D. L., Dig, D., & van Deursen, A. (2014). A study and toolkit for asynchronous programming in c#. In ICSE 2014 Proceedings of the 36th International Conference on Software Engineering (pp. 1117 - 1127). Association for Computing Machinery (ACM). https://doi.org/10.1145/2568225.2568309