on Mon Apr 11 2016, Stephen Canon <[email protected]> wrote:
> Joe’s isn’t saying that “Indexes” is more common, rather that it’s regular > (i.e. > follows the usual declension rule for plurals); there’s tradeoffs each way, > but > using the regular plural might make it more familiar for some non-native > speakers/readers. Indexes also has the disadvantage of being a verb as well as a plural noun. > > > – Steve > > On Apr 11, 2016, at 9:42 AM, Trent Nadeau via swift-evolution > <[email protected]> wrote: > > I disagree. According to both http://grammarist.com/usage/indexes-indices/ > and http://www.worldwidewords.org/qa/qa-ind2.htm, "indices" is more common > in the English-speaking world (outside of parts of America and Canada) as > well as in technical contexts. > > On Mon, Apr 11, 2016 at 12:29 PM, Joe Groff via swift-evolution > <[email protected]> wrote: > > I love irregular plurals as much as the next grammar nerd, but I think > it'd > be better to use the more regular, but still correct, plural "indexes" > rather than "indices". > > -Joe > > > On Apr 10, 2016, at 2:41 PM, Chris Lattner via swift-evolution > <[email protected]> wrote: > > > > Hello Swift community, > > > > The review of "A New Model for Collections and Indices" begins now > and > runs through April 18th. The proposal is available here: > > > > > > https://github.com/apple/swift-evolution/blob/master/proposals/0065-collections-move-indices.md > > > > > Reviews are an important part of the Swift evolution process. All > reviews should be sent to the swift-evolution mailing list at: > > https://lists.swift.org/mailman/listinfo/swift-evolution > > or, if you would like to keep your feedback private, directly to the > review manager. > > > > > > What goes into a review? > > > > The goal of the review process is to improve the proposal under > review > through constructive criticism and, eventually, determine the > direction > of Swift. When writing your review, here are some questions you might > want to answer in your review: > > > > * What is your evaluation of the proposal? > > * Is the problem being addressed significant enough to warrant a > change to Swift? > > * Does this proposal fit well with the feel and direction of Swift? > > * If you have you used other languages or libraries with a similar > feature, how do you feel that this proposal compares to those? > > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? > > > > More information about the Swift evolution process is available at > > > > https://github.com/apple/swift-evolution/blob/master/process.md > > > > Thank you, > > > > -Chris Lattner > > Review Manager > > > > > > > _______________________________________________ > > swift-evolution mailing list > > [email protected] > > https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution > > -- > > Trent Nadeau > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution -- Dave _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
