# Implicit conversion with auto constructors

**URL:** <https://forums.swift.org/t/implicit-conversion-with-auto-constructors/27892>\
**Category:** Pitches\
**Created:** [August 14, 2019, 2:41pm UTC](https://forums.swift.org/t/implicit-conversion-with-auto-constructors/27892 "2019-08-14T14:41:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gwendal.roue](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/gwendal.roue/32/13992_2.png) [@gwendal.roue](https://forums.swift.org/u/gwendal.roue)\
**Post date:** [August 14, 2019, 2:55pm UTC](https://forums.swift.org/t/implicit-conversion-with-auto-constructors/27892/4 "2019-08-14T14:55:54Z")

</div>

Hi @elhoov. This idea has been suggested many times. It is usually rejected very quickly. However, [this thread](https://forums.swift.org/t/floating-point-numbers-implicit-conversion/6129/10) is interesting because it explores many changes that would need to be performed in the language. I think it's a must-read for whoever is looking after implicit number conversion.

On top of that, Martin is right: Swift comes with many `ExpressibleBy...Literal` protocols for the last use case you suggest.

---

_[View the full topic](https://forums.swift.org/t/implicit-conversion-with-auto-constructors/27892)._
