Re: [swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

Jordon Rose from Apple said: "It's tracked by SR-3908 . (The description's a little different but it's the same underlying issue.)" -- Howard. On 21 June 2017 at 12:07, David Baraff wrote: > > On Jun 20, 2017, at 6:59 PM,

Re: [swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

There is a *bug* that the Swift people know about, but you are **meant** to be able to do this: ModuleA A.swift public protocol P { func m() -> String } extension Int: P { public func m() -> String { return "AP.m" } } ModuleB B.swift public protocol P { func m() -> String } extension

Re: [swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

> On Jun 20, 2017, at 2:25 PM, Travis Griggs wrote: > >> >> On Jun 20, 2017, at 7:02 AM, David Baraff via swift-users >> > wrote: >> >> I posted this on Apple’s developer forums, and someone suggested trying this

Re: [swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

> On Jun 20, 2017, at 7:02 AM, David Baraff via swift-users > wrote: > > I posted this on Apple’s developer forums, and someone suggested trying this > here. > Basically, see https://forums.developer.apple.com/thread/80349 >

Re: [swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

> This is not a made up situation: many people even within one company trying > to share code somewhat informally are going to write the same code to make > using CGPoint/Size/Rect easier, and now we can’t share anything safely. Well, have a look at what C++ did: Nothing ;-) — and therefore,

[swift-users] any wisdom about sharing "common" overloads/extensions in base libraries?

I posted this on Apple’s developer forums, and someone suggested trying this here. Basically, see https://forums.developer.apple.com/thread/80349 but in a nutshell: consider that a widely used class/struct (such as CGPoint) is missing some