# \[could become a pitch\] universal forwarding / implicit conversions

**URL:** <https://forums.swift.org/t/could-become-a-pitch-universal-forwarding-implicit-conversions/23179>\
**Category:** Discussion\
**Created:** [April 16, 2019, 8:01am UTC](https://forums.swift.org/t/could-become-a-pitch-universal-forwarding-implicit-conversions/23179 "2019-04-16T08:01:59Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [April 16, 2019, 2:24pm UTC](https://forums.swift.org/t/could-become-a-pitch-universal-forwarding-implicit-conversions/23179/8 "2019-04-16T14:24:39Z")

</div>

> [@jawbroken](#):
>
> When people have talked about “forwarding” they have generally meant a method of automatically forwarding certain methods and/or property accesses to an instance variable without having to manually write forwarding methods.

Yes. For reference: [[Proposal Draft] automatic protocol forwarding](https://forums.swift.org/t/proposal-draft-automatic-protocol-forwarding/817). The draft in that thread is out of date. I worked on a second draft incorporating some discussion feedback but that was never published. I will return to it if / when somebody willing to collaborate as an implementer comes along.

> [@jawbroken](#):
>
> I doubt user-defined implicit conversions will be added, for all the reasons that they were removed (e.g. significant type-checking performance issues, etc)

Swift supports implicit supertype conversions, but is very careful about what subtype relationships exist. I agree that we won't see implicit conversions outside of this narrow scope.

---

_[View the full topic](https://forums.swift.org/t/could-become-a-pitch-universal-forwarding-implicit-conversions/23179)._