4 Commits

Author	SHA1	Message	Date
Huon Wilson	80a74b4dfc	[AST] Choose an implied conformance source next to the type, if possible. ... If a conformance to a protocol is implied by several other conformances (i.e. protocol P: Equatable {} and protocol Q: Equatable {} and a type declares conformance to both P and Q), we should choose a source that's in the same file as the type, if we can, because automatic synthesis of conformances (for Equatable, Hashable, etc.) only works in that case. Fixes rdar://problem/41852654.	2018-07-06 18:24:21 +10:00
Huon Wilson	47e643af0e	[Sema] Fix synthesis of Equatable and Hashable conformances in extensions of generic types. ... https://bugs.swift.org/browse/SR-6803	2018-05-07 09:41:25 +10:00
Huon Wilson	3488a3a53b	[Sema] Allow synthesis of protocol conformances in extensions. ... This works for all protocols except for Decodable on non-final classes, because the init requirement has to be 'required' and thus in the type's declaration. Fixes most of https://bugs.swift.org/browse/SR-6803.	2018-05-07 09:41:25 +10:00
Robert Widmann	dac06898e9	[SE-0194] Deriving Collections of Enum Cases ... Implements the minimum specified by the SE-proposal. * Add the CaseIterable protocol with AllCases associatedtype and allCases requirement * Automatic synthesis occurs for "simple" enums - Caveat: Availability attributes suppress synthesis. This can be lifted in the future - Caveat: Conformance must be stated on the original type declaration (just like synthesizing Equatable/Hashable) - Caveat: Synthesis generates an [T]. A more efficient collection - possibly even a lazy one - should be put here.	2018-03-09 00:22:55 -05:00