# Properties forwarding (aliasing)

**URL:** <https://forums.swift.org/t/properties-forwarding-aliasing/14362>\
**Category:** Pitches\
**Created:** [July 10, 2018, 7:35am UTC](https://forums.swift.org/t/properties-forwarding-aliasing/14362 "2018-07-10T07:35:12Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [June 23, 2019, 1:12pm UTC](https://forums.swift.org/t/properties-forwarding-aliasing/14362/25 "2019-06-23T13:12:10Z")

</div>

> [@idrougge](#):
>
> The Kotlin language already has an idiom for specifying protocol or class conformance by forwarding its interface to a property: [https://kotlinlang.org/docs/reference/delegation.html](https://kotlinlang.org/docs/reference/delegation.html)
> 
> Note that this idiom encourages "composition over inheritance" and fits well with protocol-oriented programming.

I [pitched protocol-based forwarding](https://forums.swift.org/t/proposal-draft-automatic-protocol-forwarding/817) in the early days of Swift evolution. There are some nuances around `Self` and associated types in Swift that I don’t believe are relevant to Kotlin. There was good discussion and I started working on a second draft of the proposal. I dropped it when it became clear it was not going to make it into Swift 3. I would like to revisit that topic someday.

---

_[View the full topic](https://forums.swift.org/t/properties-forwarding-aliasing/14362)._