<div dir="ltr">That sounds like a great plan.<div><br></div><div>I can start taking a look at the initial step this weekend, or if Shawn or Max prefers they can do it too.</div><div><br></div><div>Austin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 19, 2016 at 5:29 PM, Dave Abrahams <span dir="ltr"><<a href="mailto:dabrahams@apple.com" target="_blank">dabrahams@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
on Fri Feb 19 2016, Shawn Erickson <shawnce-AT-gmail.com> wrote:<br>
<br>
</span><div><div class="h5">> I would like to make myself available for standard library work. It is more<br>
> of wheel house then compiler, etc.<br>
><br>
> -Shawn<br>
><br>
> On Fri, Feb 19, 2016 at 3:19 PM Dave Abrahams via swift-dev <<br>
> <a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> wrote:<br>
><br>
>><br>
>> on Tue Feb 16 2016, Austin Zheng <swift-dev-AT-swift.org> wrote:<br>
>><br>
>> > Hi all,<br>
>> ><br>
>> > The bug tracker contains a number of small, relatively straightforward<br>
>> > tasks and bugs marked as 'starter bugs'. What would be a good way to<br>
>> > find, start working on, or collaborate on tasks and engineering<br>
>> > projects with larger, more complex scope? I know there are Apple<br>
>> > engineers concentrating on specific subsets of Swift 3.0<br>
>> > functionality, and it would be great if there were a way for us on the<br>
>> > outside to usefully help out.<br>
>><br>
>> Hi Austin,<br>
>><br>
>> Thanks again for asking. We actually have a pretty substantial<br>
>> challenge ahead with replacing the standard library's collections and<br>
>> indices with what's in<br>
>><br>
>> <a href="https://github.com/apple/swift/blob/master/test/Prototypes/CollectionsMoveIndices.swift" rel="noreferrer" target="_blank">https://github.com/apple/swift/blob/master/test/Prototypes/CollectionsMoveIndices.swift</a><br>
>> I anticipate that the whole stdlib team may need to be involved in this<br>
>> project, which Dmitri (Cc'd) is driving, and we'd love it if you could<br>
>> help.<br>
>><br>
>> Obviously, as it hasn't gone through review yet, it needs to happen on a<br>
>> branch.<br>
>><br>
>> Does that sound interesting?<br>
<br>
</div></div>Okay, I've up a branch for you guys: swift-3-indexing-model.<br>
<br>
* You can submit pull requests against that.<br>
<br>
* There are corresponding branches in the swift-llvm and swift-clang<br>
repos that this branch will build/test against.<br>
<br>
* The branch is based on swift-3-api-guidelines, where we're doing all<br>
the renaming work associated with the new guidelines; we expect to<br>
merge that branch into master in a few days, so basing the indexing model<br>
work on it should reduce conflicts when we merge this work.<br>
<br>
Most of the stdlib team is currently occupied with other fires, but we<br>
want to move on to work on this ASAP. If it's possible for you guys to<br>
get it started in the meantime, that would be truly awesome.<br>
Unfortunately the hardest part is right at the beginning.<br>
<br>
The first step is to make the minimal changes required to get the<br>
standard library to build after replacing the Collection protocol with<br>
the three shown in the prototype. That step may not be very<br>
parallelizable and might require either close coordination or for one of<br>
you to do it alone. Tests will be horribly broken at this point, and<br>
you may have even commented out parts of the standard library, so this<br>
step requires intestinal fortitude.<br>
<br>
If parts of the library have been disabled in step 1, next you can split<br>
up the work of getting the whole library to work.<br>
<br>
At this point you should be able to mark the old Index protocols<br>
@unavailable and move on to fixing tests.<br>
<br>
How does this all sound?<br>
<br>
P.S. The Swift community is *so* awesome.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
-Dave<br>
</font></span></blockquote></div><br></div>