[swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

[Shawn Erickson]

Anything to attempt on strings? I see you are considering consolidating
down to a single index type for those, etc. Of course you also imply a
large string rework that may happen in the future.

-Shawn

On Mon, Apr 11, 2016 at 11:07 AM Dave Abrahams <dabrahams at apple.com> wrote:

>
> on Sun Apr 10 2016, Austin Zheng <austinzheng-AT-gmail.com> wrote:
>
> > I'm really sorry for dropping the ball and disappearing off the list.
> I'd like
> > to help out if I can. I'll check out the current branch tomorrow and see
> what
> > the status of the work is, but let me know if everything is done
> already/there's
> > something in particular that should be worked on.
>
> Dmitri may have other ideas, but one thing we haven't done is to take
> advantage of the new model by removing references from indices.  I'd
> like to prove that the new model does what it's supposed to.  You might
> try simplifying the indices for Set and Dictionary.  It should be
> possible to represent them as a wrapper around an Int.
>
> >
> >
> > Austin
> >
> > On Mon, Mar 21, 2016 at 11:39 AM, Shawn Erickson <shawnce at gmail.com>
> wrote:
> >
> >     Anything I can help with on this effort? It looks like things are
> moving
> >     along among the Apple folks. Not sure how to jump in without
> stepping on in
> >     flight work, etc.
> >
> >     On Tue, Mar 15, 2016 at 1:39 AM Dmitri Gribenko <gribozavr at gmail.com>
> wrote:
> >
> >     On Mon, Mar 14, 2016 at 7:59 PM, Shawn Erickson <shawnce at gmail.com>
> wrote:
> >         >
> >         >
> >         > On Thu, Mar 10, 2016 at 10:49 PM Dmitri Gribenko <
> gribozavr at gmail.com>
> >         > wrote:
> >         >>
> >         >> Hi everyone,
> >         >>
> >         >> I just wanted to announce that we have sufficient change on
> the
> >         >> swift-3-indexing-model branch so that we can build the core
> standard
> >         >> library and StdlibUnittest. We achieved this by putting the
> protocol
> >         >> new structure into place, and stubbing out with fatalError()
> or just
> >         >> commenting out parts that didn't compile. Now we have a
> baseline that
> >         >> we won't regress, and we are starting to work towards
> improving it,
> >         >> making existing tests pass, and then writing new tests, and
> >         addressing
> >         >> TODOs and FIXMEs that we left in the code as we were doing
> the first
> >         >> pass.
> >         >>
> >         >> Here's the most recent pull request from Shawn where he
> starts to fix
> >         >> the tests: https://github.com/apple/swift/pull/1632
> >         >>
> >         >> Now we are in the "massively-parallel" stage of this project
> and we,
> >         >> as always, welcome contributions to this branch!
> >         >
> >         >
> >         > FYI
> >         >
> >         > I am working on the following:
> >         >
> >         > FAIL: Swift :: 1_stdlib/StringDiagnostics.swift
> >         > FAIL: Swift ::
> 1_stdlib/StringDiagnostics_without_Foundation.swift
> >         > ...and looking at converting String.XxxxIndexes to the new
> index style
> >         while
> >         > maintaining existing public API.
> >
> >         There doesn't seem to be many tests actively failing in the
> primary
> >         testsuite, so I'll be working on making StdlibCollectionUnittest
> >         compile, which will allow us to run the validation testsuite.
> >
> >         Dmitri
> >
> >         --
> >
>  main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
> >         (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com
> >*/
> >
>
> --
> Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20160411/d7e4746f/attachment.html>