# Implementing ExpressibleByTupleLiteral: how hard?

**URL:** <https://forums.swift.org/t/implementing-expressiblebytupleliteral-how-hard/21169>\
**Category:** Compiler\
**Created:** [March 3, 2019, 8:54pm UTC](https://forums.swift.org/t/implementing-expressiblebytupleliteral-how-hard/21169 "2019-03-03T20:54:55Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![Chris\_Lattner3](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/chris_lattner3/32/348_2.png) [@Chris\_Lattner3](https://forums.swift.org/u/Chris_Lattner3)\
**Post date:** [March 9, 2019, 4:28am UTC](https://forums.swift.org/t/implementing-expressiblebytupleliteral-how-hard/21169/29 "2019-03-09T04:28:02Z")

</div>

Why wouldn't we make this match the other literals in the system? I should be able to do:

```swift
struct MyThing : TupleLiteralConvertible {
  init(tupleLiteral value: (Int, Int)) {}
}

var x : MyThing = (4, 2)

```

So yeah, we need variadic generics to make this particularly useful, but we need that anyway.

-Chris

---

_[View the full topic](https://forums.swift.org/t/implementing-expressiblebytupleliteral-how-hard/21169)._