Given the prevalence of protocols for expressing common functionality in Swift, I consider a newtype-like facility without some form of (opt-in) forwarding of protocol conformances to be too small to be useful. Indeed, I think the right feature for Swift is to add opt-in forwarding of protocol conformances without adding newtype, per my comments in Opaque result types - #177 by Douglas_Gregor.
Doug