The project would definitely be well-served by having more documentation, and 
hopefully we’ll see that grow both incrementally and in spurts.  Even writing 
tutorials, however, must be weighed against competing priorities — such as 
finishing the work for ABI stability.  My hope is we can find a balance of 
investment in helping more people in the community feel empowered to implement 
proposals in the compiler/standard library while not diluting focus from 
delivering ABI stability.

> On Aug 8, 2017, at 11:28 PM, Jonathan Hull <> wrote:
> Would it be possible to get a series of tutorials on how the systems that 
> make up Swift generally work?  In other words, what are the pieces and how do 
> they fit together?
> I think it would be useful even for people who aren’t directly implementing 
> because they can have a better idea of how difficult a change actually is.  
> It might also help some of us who have been sitting on the sideline to dip 
> our toes in the water.  I know I get a bit lost every time I try to find 
> something in the Swift source, and I am guessing I am not the only one...
> Thanks,
> Jon
>> On Aug 8, 2017, at 5:27 PM, Ted Kremenek via swift-evolution 
>> < <>> wrote:
>>> On Aug 8, 2017, at 2:29 PM, Paul Cantrell < 
>>> <>> wrote:
>>> I imagine that the core team will assist in providing implementations for 
>>> proposals that are crucial to the progress of the language and/or highly 
>>> popular — regardless of whether the proposal was authored by the core team 
>>> or a community member.
>> That is true.  Everyone’s ability to assist is ultimately balanced by their 
>> own capacity and priorities, but I think there are plenty of examples of 
>> this happening in the past.  Also, there is a increasing number of people — 
>> and not just the Core Team or compiler engineers in my team at Apple — who 
>> are becoming increasingly comfortable working with the implementation of the 
>> compiler and the standard library.
>> _______________________________________________
>> swift-evolution mailing list
>> <>

swift-evolution mailing list

Reply via email to