Re: [swift-evolution] Figuring out what you get for free

2017-09-18 Thread Félix Cloutier via swift-evolution
To be clear, I find the stdlib already fairly well-documented. I think that the problem is more important for types from projects that are unlikely to get good documentation. > Le 17 sept. 2017 à 23:43, Dimitri Racordon via swift-evolution > a écrit : > >> - In

Re: [swift-evolution] Figuring out what you get for free

2017-09-18 Thread Dimitri Racordon via swift-evolution
> - In step 2, the compiler could propose a fixit for subscript where the > unknown associated type is replaced by a placeholder. > - Fixits from steps 2, 3, and 4 should be combined together as a single fixit. Would be nice indeed. But I too believe that we could make it way easier for

Re: [swift-evolution] Figuring out what you get for free

2017-09-17 Thread Michel Fortin via swift-evolution
It could certainly be improved: - In step 2, the compiler could propose a fixit for subscript where the unknown associated type is replaced by a placeholder. - Fixits from steps 2, 3, and 4 should be combined together as a single fixit. And with this: you add the conformance to your type, Xcode

Re: [swift-evolution] Figuring out what you get for free

2017-09-17 Thread T.J. Usiyan via swift-evolution
I guess the question is, "Do we want this to be the process we expect of and explain to newcomers?" On Sun, Sep 17, 2017 at 7:32 PM, Michel Fortin via swift-evolution < swift-evolution@swift.org> wrote: > Le 17 sept. 2017 à 18:00, Félix Cloutier via swift-evolution < > swift-evolution@swift.org>

Re: [swift-evolution] Figuring out what you get for free

2017-09-17 Thread Michel Fortin via swift-evolution
> Le 17 sept. 2017 à 18:00, Félix Cloutier via swift-evolution > > a écrit : > > I found that for Sequence, but Sequence is far from the only protocol with > default implementations, and not all of them have maintainers willing to >

Re: [swift-evolution] Figuring out what you get for free

2017-09-17 Thread Félix Cloutier via swift-evolution
I found that for Sequence, but Sequence is far from the only protocol with default implementations, and not all of them have maintainers willing to write and update documentation to the degree that Apple will. Félix > Le 14 sept. 2017 à 15:10, Kyle Murray a écrit : > >

Re: [swift-evolution] Figuring out what you get for free

2017-09-15 Thread Taylor Swift via swift-evolution
i think in general the API docs could be organized in a more helpful way. On Fri, Sep 15, 2017 at 3:30 PM, Kyle Murray via swift-evolution < swift-evolution@swift.org> wrote: > > However, I find that I'm having trouble figuring out what I get for free > when I implement a protocol. In principle,

Re: [swift-evolution] Figuring out what you get for free

2017-09-15 Thread Kyle Murray via swift-evolution
> However, I find that I'm having trouble figuring out what I get for free when > I implement a protocol. In principle, I like conditional conformances and > synthesized implementation of protocol methods, but I find that they both > make it harder to figure out what I need to implement, and

[swift-evolution] Figuring out what you get for free

2017-09-12 Thread Félix Cloutier via swift-evolution
If you look at the source for Sequence , you can see that the protocol declares a ton of methods and properties; but in fact, all you need to provide is Element, Iterator and makeIterator. The rest comes for