This doc has been moved to A Google doc to allow easier commenting and collaboration.
NOTE: This is a super sketchy attempt to describe an alternative approach to solve the problems outlined in SE-0244 - Opaque Result Types. This document is intended to be read side-by-side with that proposal.
Character processing is everywhere - particularly when working with ASCII. However, Swift's support for working with it is awkward and suboptimal. This proposal seeks to improve character processing support by allowing Swift integers to be written using single quoted character literals, which is much more consistent with other languages and will reduce a point of friction in string processing code.
Modern Cocoa development involves a lot of asynchronous programming using closures and completion handlers, but these APIs are hard to use. This gets particularly problematic when many asynchronous operations are used, error handling is required, or control flow between asynchronous calls gets complicated. This proposal describes a language extension to make this a lot more natural and less error prone.
This paper introduces a first class Coroutine model to Swift. Functions can opt into to being async, allowing the programmer to compose complex logic involving asynchronous operations, leaving the compiler in charge of producing the necessary closures and state machines to implement that logic.