[swift-evolution] Synthesizing Equatable, Hashable, and Comparable for tuple types
clattner at nondot.org
Mon Nov 20 20:51:13 CST 2017
On Nov 20, 2017, at 6:31 PM, Tony Allevato <tony.allevato at gmail.com> wrote:
> So (borrowing C++-ish notation), a function of type `(Args...) -> Result` would become sugar for something like `Function<Args..., Result>`? That certainly makes sense.
> How would throw-ness be handled—would we need ThrowingFunction and Function, with the ability to coerce Function -> ThrowingFunction? (Async might pose similar issues?)
Right, there are several ways we could express that which would have to be designed. There are other questions as well: e.g. how do we represent inout?
More information about the swift-evolution