The Week Of Monday 7 December 2015 Archives by date

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...

Starting: Mon Dec 7 00:02:25 CST 2015
Ending: Sun Dec 13 23:56:51 CST 2015
Messages: 1444

• [swift-evolution] Proposal: Tuple Convertible   John McCall
• [swift-evolution] Overloading assignment operator   Don Wills
• [swift-evolution] C-style For Loops   Brent Royal-Gordon
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   thorsten at portableinnovations.de
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   thorsten at portableinnovations.de
• [swift-evolution] Overloading assignment operator   John McCall
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Tino Heth
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Brent Royal-Gordon
• [swift-evolution] Proposal: Auto-convert for numbers when safe   Manav Gabhawala
• [swift-evolution] Proposal: A standard library Fraction type   Harlan Haskins
• [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Kevin Ballard
• [swift-evolution] Auto-convert for numbers when safe   William Shipley
• [swift-evolution] throws!   Jonathan Hull
• [swift-evolution] Adding an operator to return the "lowest common type" of two types?   William Shipley
• [swift-evolution] throws!   Adrian Kashivskyy
• [swift-evolution] Adding an operator to return the "lowest common type" of two types?   Martin Kühl
• [swift-evolution] Proposal: A standard library Fraction type   T.J. Usiyan
• [swift-evolution] Proposal: A standard library Fraction type   Davide De Franceschi
• [swift-evolution] throws!   Jonathan Hull
• [swift-evolution] Proposal: A standard library Fraction type   Adrian Kashivskyy
• [swift-evolution] Review: SE-0007 (Remove C-style for-loops with conditions and incrementers)   Michael Mayer
• [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Andrew
• [swift-evolution] Allow Selectors to be used as Closures   Chris Byatt
• [swift-evolution] Will these two features be included in Swift 3?   tuuranton at tutanota.de
• [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Per Melin
• [swift-evolution] Will these two features be included in Swift 3?   Krzysztof Siejkowski
• [swift-evolution] Adding an operator to return the "lowest common type" of two types?   Jonathan Hull
• [swift-evolution] Will these two features be included in Swift 3?   Krzysztof Siejkowski
• [swift-evolution] Will these two features be included in Swift 3?   Davide De Franceschi
• [swift-evolution] Will these two features be included in Swift 3?   Krzysztof Siejkowski
• [swift-evolution] zip3, zip4, ...   Vinicius Vendramini
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Will these two features be included in Swift 3?   Davide De Franceschi
• [swift-evolution] zip3, zip4, ...   Davide De Franceschi
• [swift-evolution] Overloading assignment operator   Matthew Johnson
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Matthew Johnson
• [swift-evolution] Will these two features be included in Swift 3?   Daniel Steinberg
• [swift-evolution] Proposal: Tuple Convertible   Tal Atlas
• [swift-evolution] HTTP webserver protocol's   Coen Wessels
• [swift-evolution] Proposal: A standard library Fraction type   Stephen Canon
• [swift-evolution] Overloading assignment operator   Don Wills
• [swift-evolution] zip3, zip4, ...   Matthew Johnson
• [swift-evolution] access control proposal   plx
• [swift-evolution] do try catch?   Don Arnel
• [swift-evolution] do try catch?   王巍
• [swift-evolution] Proposal: A standard library Fraction type   T.J. Usiyan
• [swift-evolution] Proposal: A standard library Fraction type   plx
• [swift-evolution] Proposal: Allow willChange and didChange observers on a property   plx
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Proposal: A standard library Fraction type   Stephen Canon
• [swift-evolution] Proposal: A standard library Fraction type   Matthew Johnson
• [swift-evolution] do try catch?   Liam Butler-Lawrence
• [swift-evolution] HTTP webserver protocol's   John Siracusa
• [swift-evolution] Proposal: A standard library Fraction type   T.J. Usiyan
• [swift-evolution] Proposal: A standard library Fraction type   T.J. Usiyan
• [swift-evolution] do try catch?   Davide De Franceschi
• [swift-evolution] Overloading assignment operator   Stephen Celis
• [swift-evolution] Straw Poll. Re: Method cascading (was Re: Request for Discussion: Setup closures)   Erica Sadun
• [swift-evolution] do try catch?   Kametrixom Tikara
• [swift-evolution] Proposal: failable numeric conversion initializers   thorsten at portableinnovations.de
• [swift-evolution] Proposal: A standard library Fraction type   Matthew Johnson
• [swift-evolution] Proposal: Change of syntax for class protocols   Matthew Cheok
• [swift-evolution] ternary operator ?: suggestion   thorsten at portableinnovations.de
• [swift-evolution] Unify `static` and `class` keywords   an0
• [swift-evolution] throws!   Stephen Canon
• [swift-evolution] Straw Poll. Re: Method cascading (was Re: Request for Discussion: Setup closures)   Sean Heber
• [swift-evolution] HTTP webserver protocol's   Lukas Stabe
• [swift-evolution] Adding an operator to return the "lowest common type" of two types?   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Change of syntax for class protocols   Sean Heber
• [swift-evolution] Make access control private by default.   Amir Michail
• [swift-evolution] Make access control private by default.   Stephen Celis
• [swift-evolution] Make access control private by default.   Amir Michail
• [swift-evolution] Proposal: Change of syntax for class protocols   Stephen Celis
• [swift-evolution] Make access control private by default.   Stephen Celis
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Joe Groff
• [swift-evolution] Proposal: Change of syntax for class protocols   David Owens II
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Make access control private by default.   Amir Michail
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Joe Groff
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Joe Groff
• [swift-evolution] Proposal: Change of syntax for class protocols   Vivien Leroy
• [swift-evolution] Proposal: Change of syntax for class protocols   Joe Groff
• [swift-evolution] Proposal: Change of syntax for class protocols   Sean Heber
• [swift-evolution] Straw Poll. Re: Method cascading (was Re: Request for Discussion: Setup closures)   Joe Groff
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Proposal: Change of syntax for class protocols   Felix Gabel
• [swift-evolution] HTTP webserver protocol's   Simon Pilkington
• [swift-evolution] HTTP webserver protocol's   Simon Pilkington
• [swift-evolution] Proposal: Change of syntax for class protocols   Matthew Cheok
• [swift-evolution] Requiring self. to access properties and methods   Florian Reinhart
• [swift-evolution] do try catch?   Liam Butler-Lawrence
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Nick Shelley
• [swift-evolution] Proposal: failable numeric conversion initializers   Dmitri Gribenko
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Stephen Celis
• [swift-evolution] HTTP webserver protocol's   Maxthon Chan
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Make access control private by default.   Javier Soto
• [swift-evolution] Make access control private by default.   Stephen Celis
• [swift-evolution] Unify `static` and `class` keywords   David Hart
• [swift-evolution] Proposal: failable numeric conversion initializers   Stephen Canon
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Review: SE-0007 (Remove C-style for-loops with conditions and incrementers)   Alex Chan
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Jordan Rose
• [swift-evolution] Straw Poll. Re: Method cascading (was Re: Request for Discussion: Setup closures)   Tino Heth
• [swift-evolution] Requiring self. to access properties and methods   Johan Jensen
• [swift-evolution] Make access control private by default.   Matthew Johnson
• [swift-evolution] Unify `static` and `class` keywords   J. Cheyo Jimenez
• [swift-evolution] Unify `static` and `class` keywords   Matthew Johnson
• [swift-evolution] Swift standard libraries should support simple 2d graphics and music on all platforms.   Amir Michail
• [swift-evolution] Will these two features be included in Swift 3?   Radosław Pietruszewski
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Joe Groff
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Slava Pestov
• [swift-evolution] Proposal: failable numeric conversion initializers   Matthew Johnson
• [swift-evolution] Will these two features be included in Swift 3?   Joe Groff
• [swift-evolution] Will these two features be included in Swift 3?   Slava Pestov
• [swift-evolution] Make access control private by default.   Jordan Rose
• [swift-evolution] do try catch?   Slava Pestov
• [swift-evolution] HTTP webserver protocol's   Paul Cantrell
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Will these two features be included in Swift 3?   Jacob Bandes-Storch
• [swift-evolution] Final by default for classes and methods   Javier Soto
• [swift-evolution] Final by default for classes and methods   Slava Pestov
• [swift-evolution] Final by default for classes and methods   Joe Groff
• [swift-evolution] Final by default for classes and methods   Kevin Lundberg
• [swift-evolution] Unify `static` and `class` keywords   John McCall
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   David Hart
• [swift-evolution] Final by default for classes and methods   Javier Soto
• [swift-evolution] Control Flow Expressions   Cameron Knight
• [swift-evolution] Final by default for classes and methods   Riley Testut
• [swift-evolution] Final by default for classes and methods   Stephen Celis
• [swift-evolution] Unify `static` and `class` keywords   an0
• [swift-evolution] Final by default for classes and methods   David Owens II
• [swift-evolution] Unify `static` and `class` keywords   an0
• [swift-evolution] Unify `static` and `class` keywords   Matthew Johnson
• [swift-evolution] do try catch?   Kametrixom Tikara
• [swift-evolution] Proposal: Change of syntax for class protocols   Riley Testut
• [swift-evolution] Final by default for classes and methods   Riley Testut
• [swift-evolution] Final by default for classes and methods   Kevin Lundberg
• [swift-evolution] Unify `static` and `class` keywords   an0
• [swift-evolution] Unify `static` and `class` keywords   John McCall
• [swift-evolution] Proposal: Change of syntax for class protocols   Austin Zheng
• [swift-evolution] Final by default for classes and methods   Tino Heth
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Final by default for classes and methods   Matthew Johnson
• [swift-evolution] Final by default for classes and methods   Matthew Johnson
• [swift-evolution] Proposal: Allow Getters and Setters to Throw   Jordan Rose
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Dmitri Gribenko
• [swift-evolution] Unify `static` and `class` keywords   Matthew Johnson
• [swift-evolution] Final by default for classes and methods   Sean Heber
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Joe Groff
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] C-style For Loops   Colin Barrett
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Unify `static` and `class` keywords   Rudolf Adamkovic
• [swift-evolution] Print stack trace for fatalError   Harlan Haskins
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Mark Lacey
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   an0
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Dmitri Gribenko
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Joe Groff
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Colin Barrett
• [swift-evolution] restricting AnySequence.init   Maxim Moiseev
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Breckin Loggins
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   Douglas Gregor
• [swift-evolution] Proposal: Change of syntax for class protocols   Guillaume Lessard
• [swift-evolution] restricting AnySequence.init   Dmitri Gribenko
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   David Owens II
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   krzysztof at siejkowski.net
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Alex Lew
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Jacob Bandes-Storch
• [swift-evolution] Proposal: Change of syntax for class protocols   Joe Groff
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   David Owens II
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Dmitri Gribenko
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   ilya
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Joe Groff
• [swift-evolution] Print stack trace for fatalError   Radoslaw Pietruszewski
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] C-style For Loops   Tyler Cloutier
• [swift-evolution] Control Flow Expressions   J. Cheyo Jimenez
• [swift-evolution] protocol based invocation forwarding   David Owens II
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   Paul Cantrell
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Colin Barrett
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Kevin Ballard
• [swift-evolution] Control Flow Expressions   J. Cheyo Jimenez
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Kevin Ballard
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Joe Groff
• [swift-evolution] Control Flow Expressions   Riley Testut
• [swift-evolution] Control Flow Expressions   Riley Testut
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Print stack trace for fatalError   Harlan Haskins
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   Kevin Ballard
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   David Farler
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Colin Barrett
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Per Melin
• [swift-evolution] Proposal: Change of syntax for class protocols   Douglas Gregor
• [swift-evolution] Swift standard libraries should support simple 2d graphics and music on all platforms.   Amir Michail
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   krzysztof at siejkowski.net
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Final by default for classes and methods   Joseph Lord
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Nate Cook
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Proposal: Typed throws   Russ Bishop
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   ilya
• [swift-evolution] Proposal: Change of syntax for class protocols   Felix Gabel
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Dmitri Gribenko
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Jacob Bandes-Storch
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   T.J. Usiyan
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Auto-convert for numbers when safe   Chris Lattner
• [swift-evolution] Proposal: A standard library Fraction type   T.J. Usiyan
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Chris Lattner
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Chris Lattner
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Chris Lattner
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Jacob Bandes-Storch
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   ilya
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   John McCall
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Mark Lacey
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Joe Groff
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Brent Royal-Gordon
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   John McCall
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   David Farler
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   ilya
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] do try catch?   Chris Lattner
• [swift-evolution] C-style For Loops   Ray Fix
• [swift-evolution] Swift standard libraries should support simple 2d graphics and music on all platforms.   Chris Lattner
• [swift-evolution] lazy keyword vs lazy initialization pattern   Chris Lattner
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Chris Lattner
• [swift-evolution] Proposal: Typed throws   Andrew Bennett
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Chris Lattner
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Dmitri Gribenko
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Chris Lattner
• [swift-evolution] C-style For Loops   David Waite
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Brent Royal-Gordon
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Dmitri Gribenko
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Brent Royal-Gordon
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Dmitri Gribenko
• [swift-evolution] Unify `static` and `class` keywords   Chris Lattner
• [swift-evolution] Proposal: Typed throws   David Owens II
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Andrew Bennett
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Matthew Johnson
• [swift-evolution] Proposal: Typed throws   Andrew Bennett
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Chris Lattner
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Erica Sadun
• [swift-evolution] HTTP webserver protocol's   Brent Royal-Gordon
• [swift-evolution] Proposal: Typed throws   David Waite
• [swift-evolution] Final by default for classes and methods   Kevin Ballard
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Final by default for classes and methods   David Waite
• [swift-evolution] Unify `static` and `class` keywords   Chris Lattner
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Kevin Ballard
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Joe Groff
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Kevin Lundberg
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Austin Zheng
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Final by default for classes and methods   Matthew Johnson
• [swift-evolution] Unify `static` and `class` keywords   Matthew Johnson
• [swift-evolution] Proposal: Add @noescape to the transform parameter of 'SequenceType.flatMap'   Meador Inge
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   Matthew Johnson
• [swift-evolution] HTTP webserver protocol's   Lukas Stabe
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Alex Lew
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Unify `static` and `class` keywords   J. Cheyo Jimenez
• [swift-evolution] Final by default for classes and methods   John McCall
• [swift-evolution] do try catch?   Liam Butler-Lawrence
• [swift-evolution] Final by default for classes and methods   Javier Soto
• [swift-evolution] HTTP webserver protocol's   Simon Pilkington
• [swift-evolution] Proposal: Typed throws   Russ Bishop
• [swift-evolution] Proposal: Typed throws   Austin Zheng
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] Proposal: Specifying local parameter names for closures to generate strict argument list   Adrian Zubarev
• [swift-evolution] Proposal: Change of syntax for class protocols   Adrian Zubarev
• [swift-evolution] Final by default for classes and methods   ilya
• [swift-evolution] [swift-corelibs-dev] Proposal: add `noescape` attribute to public API (particularly libdispatch)   Jacob Bandes-Storch
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Daniel Vollmer
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] Proposal: Change of syntax for class protocols   Felix Gabel
• [swift-evolution] isEqual to replace == Equatable Requirement   Richard Fox
• [swift-evolution] isEqual to replace == Equatable Requirement   Nicky Gerritsen
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Andrew Bennett
• [swift-evolution] Proposal: Closures capture weak by default   Andrew Bennett
• [swift-evolution] Will these two features be included in Swift 3?   tuuranton at tutanota.de
• [swift-evolution] Proposal: Closures capture weak by default   ilya
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Observable event streams in Swift?   Aron Allen
• [swift-evolution] Unify `static` and `class` keywords   Daniel Valls Estella
• [swift-evolution] isEqual to replace == Equatable Requirement   David Hart
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Amir Michail
• [swift-evolution] Optional precondition after else and #else   Amir Michail
• [swift-evolution] Unify `static` and `class` keywords   an0
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   Krzysztof Siejkowski
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Kevin Lundberg
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   plx
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Amir Michail
• [swift-evolution] isEqual to replace == Equatable Requirement   Stephen Celis
• [swift-evolution] Proposal: Closures capture weak by default   Javier Soto
• [swift-evolution] Final by default for classes and methods   Matthew Johnson
• [swift-evolution] Will these two features be included in Swift 3?   Simon Pilkington
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Javier Soto
• [swift-evolution] Proposal: Closures capture weak by default   Joe Groff
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Closures capture weak by default   Joe Groff
• [swift-evolution] Proposal: Closures capture weak by default   ilya
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   plx
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Proposal: extend Optional-specific syntax to arbitrary types with CustomOptionalConvertible   Matthew Johnson
• [swift-evolution] Proposal: Change of syntax for class protocols   Daniel Valls Estella
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Michael Buckley
• [swift-evolution] Unify `static` and `class` keywords   Daniel Valls Estella
• [swift-evolution] Proposal: Change of syntax for class protocols   Daniel Valls Estella
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Proposal: Change of syntax for class protocols   Stephen Celis
• [swift-evolution] Proposal: Closures capture weak by default   Paul Cantrell
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Proposal: Change of syntax for class protocols   Daniel Valls Estella
• [swift-evolution] Proposal: Closures capture weak by default   Gwendal Roué
• [swift-evolution] Proposal: Closures capture weak by default   Gwendal Roué
• [swift-evolution] Proposal: Change of syntax for class protocols   Felix Gabel
• [swift-evolution] Proposal: Improve switch control flow substituting fallthrough with a more safe one   Jacopo Andrea Giola
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   John McCall
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Closures capture weak by default   Joe Groff
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Joe Groff
• [swift-evolution] isEqual to replace == Equatable Requirement   Richard Fox
• [swift-evolution] Calling default implementation of protocols   Mateusz Zajac
• [swift-evolution] protocol based invocation forwarding   Matthew Johnson
• [swift-evolution] Proposal: Closures capture weak by default   ilya
• [swift-evolution] isEqual to replace == Equatable Requirement   David Hart
• [swift-evolution] protocol based invocation forwarding   Joe Groff
• [swift-evolution] isEqual to replace == Equatable Requirement   Joe Groff
• [swift-evolution] protocol based invocation forwarding   Matthew Johnson
• [swift-evolution] Proposal: Typed throws   David Owens II
• [swift-evolution] access control proposal   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Typed throws   Matthew Johnson
• [swift-evolution] Add a type like Double but with much more precision?   tuuranton at tutanota.de
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] else clause for loops like that in Python   Amir Michail
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Joe Groff
• [swift-evolution] Proposal: Closures capture weak by default   Gwendal Roué
• [swift-evolution] Proposal: Closures capture weak by default   Joe Groff
• [swift-evolution] Proposal - Allow properties in Extensions   Kevin Kachikian
• [swift-evolution] Review on SE-0007 (Remove C-style for-loops with conditions and incrementers)   Nicky Gerritsen
• [swift-evolution] Proposal: Closures capture weak by default   Gwendal Roué
• [swift-evolution] Proposal: Typed throws   John McCall
• [swift-evolution] Proposal: Change of syntax for class protocols   Daniel Valls Estella
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Kyle Bashour
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   John McCall
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Austin Zheng
• [swift-evolution] Remove forEach?   Chris Eidhof
• [swift-evolution] Proposal: Improve switch control flow substituting fallthrough with a more safe one   Jacopo Andrea Giola
• [swift-evolution] Proposal: Closures capture weak by default   Matthew Johnson
• [swift-evolution] Proposal: Closures capture weak by default   Kevin Ballard
• [swift-evolution] Calling default implementation of protocols   Gwendal Roué
• [swift-evolution] Run Swift code at compile time   Alejandro Martinez
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Charles Srstka
• [swift-evolution] Empower String type with regular expression   Jerome Paschoud
• [swift-evolution] Remove forEach?   Sean Heber
• [swift-evolution] Proposal: Change of syntax for class protocols   Guillaume Lessard
• [swift-evolution] Remove forEach?   Kevin Kachikian
• [swift-evolution] Empower String type with regular expression   David Waite
• [swift-evolution] Proposal: Change rules for implicit captures due to nested closure captures   Kevin Ballard
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Brent Royal-Gordon
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Michael Buckley
• [swift-evolution] protocol based invocation forwarding   Joe Groff
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Donnacha Oisín Kidney
• [swift-evolution] Will these two features be included in Swift 3?   tuuranton at tutanota.de
• [swift-evolution] else clause for loops like that in Python   Alex Chan
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] repeat loop enhancement   Jason Pollack
• [swift-evolution] Remove forEach?   Erica Sadun
• [swift-evolution] repeat loop enhancement   Kevin Kachikian
• [swift-evolution] Remove forEach?   Chris Eidhof
• [swift-evolution] Add a type like Double but with much more precision?   Brent Royal-Gordon
• [swift-evolution] repeat loop enhancement   Stephen Celis
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Brent Royal-Gordon
• [swift-evolution] else clause for loops like that in Python   Amir Michail
• [swift-evolution] Remove forEach?   Joe Groff
• [swift-evolution] Add a type like Double but with much more precision?   Joe Groff
• [swift-evolution] Add a type like Double but with much more precision?   Joe Groff
• [swift-evolution] Remove forEach?   André Videla
• [swift-evolution] Run Swift code at compile time   Andrew Bennett
• [swift-evolution] Will these two features be included in Swift 3?   Alex Lew
• [swift-evolution] repeat loop enhancement   Erica Sadun
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Brent Royal-Gordon
• [swift-evolution] protocol based invocation forwarding   Matthew Johnson
• [swift-evolution] Empower String type with regular expression   Brent Royal-Gordon
• [swift-evolution] Remove forEach?   Brent Royal-Gordon
• [swift-evolution] else clause for loops like that in Python   Brent Royal-Gordon
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Proposal: Closures capture weak by default   Andrew Bennett
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] Proposal: Allow Getters and Setters to Throw   Adrian Kashivskyy
• [swift-evolution] Proposal: Closures capture weak by default   Kevin Ballard
• [swift-evolution] Empower String type with regular expression   Kametrixom Tikara
• [swift-evolution] Proposal: Closures capture weak by default   Andrew Bennett
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] else clause for loops like that in Python   Amir Michail
• [swift-evolution] Empower String type with regular expression   Jacob Bandes-Storch
• [swift-evolution] Optional precondition after else and #else   Adrian Kashivskyy
• [swift-evolution] Optional precondition after else and #else   Jordan Rose
• [swift-evolution] Unify `static` and `class` keywords   Jordan Rose
• [swift-evolution] Proposal: Allow Getters and Setters to Throw   Brent Royal-Gordon
• [swift-evolution] Optional precondition after else and #else   Amir Michail
• [swift-evolution] access control proposal   Jordan Rose
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Amir Michail
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jordan Rose
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Adrian Kashivskyy
• [swift-evolution] Remove forEach?   Tyler Cloutier
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Amir Michail
• [swift-evolution] Proposal: Closures capture weak by default   Jordan Rose
• [swift-evolution] Calling default implementation of protocols   Jordan Rose
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Adrian Kashivskyy
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Amir Michail
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Joe Groff
• [swift-evolution] Proposal: remove "assert" and always use "precondition" instead.   Adrian Kashivskyy
• [swift-evolution] Proposal: Change rules for implicit captures due to nested closure captures   Jordan Rose
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Jordan Rose
• [swift-evolution] else clause for loops like that in Python   Jordan Rose
• [swift-evolution] Remove forEach?   Jordan Rose
• [swift-evolution] Remove forEach?   Nate Cook
• [swift-evolution] repeat loop enhancement   Jordan Rose
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Jordan Rose
• [swift-evolution] Proposal: Change rules for implicit captures due to nested closure captures   Kevin Ballard
• [swift-evolution] Proposal: Allow Getters and Setters to Throw   Jordan Rose
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jordan Rose
• [swift-evolution] repeat loop enhancement   Daniel Steinberg
• [swift-evolution] repeat loop enhancement   Jacob Bandes-Storch
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Lukas Stabe
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Brent Royal-Gordon
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Jordan Rose
• [swift-evolution] Proposal: Allow Getters and Setters to Throw   Brent Royal-Gordon
• [swift-evolution] Discussion: Move range (..., ..<) to a range() function   Brent Royal-Gordon
• [swift-evolution] else clause for loops like that in Python   Brent Royal-Gordon
• [swift-evolution] else clause for loops like that in Python   Donnacha Oisín Kidney
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Kevin Ballard
• [swift-evolution] else clause for loops like that in Python   Donnacha Oisín Kidney
• [swift-evolution] isEqual to replace == Equatable Requirement   Ling Wang
• [swift-evolution] Remove forEach?   Chris Eidhof
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Michael Buckley
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Remove forEach?   Tyler Cloutier
• [swift-evolution] Calling default implementation of protocols   Mateusz Zając
• [swift-evolution] repeat loop enhancement   Kenny Leung
• [swift-evolution] repeat loop enhancement   Eli Hini
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Chris Lattner
• [swift-evolution] Proposal - Allow properties in Extensions   Chris Lattner
• [swift-evolution] Run Swift code at compile time   Chris Lattner
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Empower String type with regular expression   Chris Lattner
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal - Allow properties in Extensions   Kevin Kachikian
• [swift-evolution] Print stack trace for fatalError   Harlan Haskins
• [swift-evolution] Unify `static` and `class` keywords   Chris Lattner
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   Chris Lattner
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Chris Lattner
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Chris Lattner
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Jacob Bandes-Storch
• [swift-evolution] repeat loop enhancement   Chris Lattner
• [swift-evolution] Print stack trace for fatalError   Chris Lattner
• [swift-evolution] Will these two features be included in Swift 3?   krzysztof at siejkowski.net
• [swift-evolution] Unify `static` and `class` keywords   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Chris Lattner
• [swift-evolution] repeat loop enhancement   André Videla
• [swift-evolution] repeat loop enhancement   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Jacob Bandes-Storch
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Chris Lattner
• [swift-evolution] Print stack trace for fatalError   Greg Parker
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Alex Lew
• [swift-evolution] Polymorphic behavior for overloaded == (and other) operators   Frederick Kellison-Linn
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Greg Parker
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Greg Parker
• [swift-evolution] Inheritance with a Constrain   Thane Gill
• [swift-evolution] protocol based invocation forwarding   Alejandro Martinez
• [swift-evolution] Run Swift code at compile time   Alejandro Martinez
• [swift-evolution] Covariance and Contravariance   Simon Pilkington
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Covariance and Contravariance   John McCall
• [swift-evolution] else clause for loops like that in Python   Kametrixom Tikara
• [swift-evolution] protocol based invocation forwarding   David Owens II
• [swift-evolution] Run Swift code at compile time   T.J. Usiyan
• [swift-evolution] Covariance and Contravariance   André Videla
• [swift-evolution] Inheritance with a Constrain   Kevin Wooten
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   T.J. Usiyan
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Review on SE-0007 (Remove C-style for-loops with conditions and incrementers)   Michael Henson
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   T.J. Usiyan
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Al Skipp
• [swift-evolution] ? suffix for <, >, =?utf-8?Q?<=3D=2C >=3D_?=comparisons with optionals to prevent subtle bugs   Lucas Derraugh
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Al Skipp
• [swift-evolution] List of all Enum values (for simple enums)   Brent Royal-Gordon
• [swift-evolution] access control proposal   Stephen Celis
• [swift-evolution] List of all Enum values (for simple enums)   Brent Royal-Gordon
• [swift-evolution] List of all Enum values (for simple enums)   Kevin Wooten
• [swift-evolution] Remove forEach?   Stephen Celis
• [swift-evolution] repeat loop enhancement   Daniel Steinberg
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Amir Michail
• [swift-evolution] repeat loop enhancement   Jason Pollack
• [swift-evolution] repeat loop enhancement   Stephen Celis
• [swift-evolution] repeat loop enhancement   Liam Butler-Lawrence
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] repeat loop enhancement   Jason Pollack
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Making asynchronous operations first-class citizens in Swift   Tommy van der Vorst
• [swift-evolution] SwiftyBeaver Logger supports Swift Package Manager   Sebastian Kreutzberger
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Remove forEach?   David Owens II
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   thorsten at portableinnovations.de
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] access control proposal   John McCall
• [swift-evolution] SwiftyBeaver Logger supports Swift Package Manager   Jordan Rose
• [swift-evolution] Remove forEach?   Joe Groff
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   Paul Cantrell
• [swift-evolution] What is the real reason for wanting to remove the C style for loop?   Amir Michail
• [swift-evolution] Covariance and Contravariance   Joe Groff
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Joe Groff
• [swift-evolution] Remove forEach?   Sean Heber
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Swift Core Crypto   Travis Beech
• [swift-evolution] Remove forEach?   J. Cheyo Jimenez
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   thorsten at portableinnovations.de
• [swift-evolution] access control proposal   John McCall
• [swift-evolution] Remove forEach?   Matthew Johnson
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   thorsten at portableinnovations.de
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Erica Sadun
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] access control proposal   John McCall
• [swift-evolution] List of all Enum values (for simple enums)   David Waite
• [swift-evolution] Remove forEach?   Guillaume Lessard
• [swift-evolution] [swift-corelibs-dev] Proposal: add `noescape` attribute to public API (particularly libdispatch)   Philippe Hausler
• [swift-evolution] Remove forEach?   Guillaume Lessard
• [swift-evolution] Searchable Swift Package Manager index?   Matias Piipari
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Al Skipp
• [swift-evolution] Searchable Swift Package Manager index?   Adrian Kashivskyy
• [swift-evolution] Remove forEach?   Donnacha Oisín Kidney
• [swift-evolution] Searchable Swift Package Manager index?   Gwendal Roué
• [swift-evolution] List of all Enum values (for simple enums)   Jacob Bandes-Storch
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Chris Lattner
• [swift-evolution] Searchable Swift Package Manager index?   Jonathan Allured
• [swift-evolution] What is the real reason for wanting to remove the C style for loop?   Douglas Gregor
• [swift-evolution] Searchable Swift Package Manager index?   Matias Piipari
• [swift-evolution] Making asynchronous operations first-class citizens in Swift   Jordan Rose
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Alex Lew
• [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Al Skipp
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Making asynchronous operations first-class citizens in Swift   Dan Stenmark
• [swift-evolution] List of all Enum values (for simple enums)   Joe Groff
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Philippe Hausler
• [swift-evolution] Remove forEach?   Joe Groff
• [swift-evolution] Remove forEach?   Kevin Ballard
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Developer
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Dmitri Gribenko
• [swift-evolution] Covariance and Contravariance   Michel Fortin
• [swift-evolution] Extending the for loop to have multiple clauses   Chris Eidhof
• [swift-evolution] Swift Core Crypto   Brent Royal-Gordon
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] Proposal: Stored properties for enums   Tommy van der Vorst
• [swift-evolution] Extending the for loop to have multiple clauses   krzysztof at siejkowski.net
• [swift-evolution] Extending the for loop to have multiple clauses   ilya
• [swift-evolution] Extending the for loop to have multiple clauses   Jacob Bandes-Storch
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Brent Royal-Gordon
• [swift-evolution] repeat loop enhancement   Tyler Cloutier
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Joe Groff
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Andrew Bennett
• [swift-evolution] Proposal: Stored properties for enums   Dave DeLong
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] repeat loop enhancement   Tyler Cloutier
• [swift-evolution] Extending the for loop to have multiple clauses   Chris Eidhof
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Proposal: Stored properties for enums   Gwendal Roué
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Brent Royal-Gordon
• [swift-evolution] Remove forEach?   Chris Eidhof
• [swift-evolution] repeat loop enhancement   Brent Royal-Gordon
• [swift-evolution] repeat loop enhancement   Sean Heber
• [swift-evolution] repeat loop enhancement   Tyler Cloutier
• [swift-evolution] Proposal: Stored properties for enums   Frederick Kellison-Linn
• [swift-evolution] repeat loop enhancement   Brent Royal-Gordon
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Amir Michail
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] repeat loop enhancement   Tyler Cloutier
• [swift-evolution] Extending the for loop to have multiple clauses   J. Cheyo Jimenez
• [swift-evolution] Extending the for loop to have multiple clauses   Frederick Kellison-Linn
• [swift-evolution] repeat loop enhancement   Sean Heber
• [swift-evolution] List of all Enum values (for simple enums)   David Waite
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Extending the for loop to have multiple clauses   Douglas Gregor
• [swift-evolution] Extending the for loop to have multiple clauses   Al Skipp
• [swift-evolution] Extending the for loop to have multiple clauses   Brent Royal-Gordon
• [swift-evolution] Proposal: Stored properties for enums   Tommy van der Vorst
• [swift-evolution] Remove forEach?   Joe Groff
• [swift-evolution] Extending the for loop to have multiple clauses   Douglas Gregor
• [swift-evolution] repeat loop enhancement   Tyler Cloutier
• [swift-evolution] Extending the for loop to have multiple clauses   ilya
• [swift-evolution] Extending the for loop to have multiple clauses   Maxwell Swadling
• [swift-evolution] Extending the for loop to have multiple clauses   ilya
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Dmitri Gribenko
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] repeat loop enhancement   Michel Fortin
• [swift-evolution] Extending the for loop to have multiple clauses   Chris Eidhof
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Jean-Daniel Dupas
• [swift-evolution] Extending the for loop to have multiple clauses   Douglas Gregor
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Covariance and Contravariance   John McCall
• [swift-evolution] Extending the for loop to have multiple clauses   David Waite
• [swift-evolution] Extending the for loop to have multiple clauses   Colin Barrett
• [swift-evolution] Remove forEach?   Chris Lattner
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Chris Lattner
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Charles Srstka
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Charles Srstka
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Chris Lattner
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Developer
• [swift-evolution] Remove default case in switch-case   Mustafa Yusuf
• [swift-evolution] Remove default case in switch-case   Chris Lattner
• [swift-evolution] Proposal: An Either Type in the STL   Developer
• [swift-evolution] Proposal: Stored properties for enums   Alex Lew
• [swift-evolution] Remove default case in switch-case   Jacob Bandes-Storch
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Chris Lattner
• [swift-evolution] Swift Core Crypto   Travis Beech
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Developer
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Amir Michail
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Amir Michail
• [swift-evolution] Proposal: Change Obj-C name for nested types to include enclosing types   Kevin Ballard
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Ilias Karim
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Jacob Bandes-Storch
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Alex Chan
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Joe Groff
• [swift-evolution] Proposal: An Either Type in the STL   Ilias Karim
• [swift-evolution] Proposal: Stored properties for enums   Tommy van der Vorst
• [swift-evolution] Proposal: An Either Type in the STL   Jacob Bandes-Storch
• [swift-evolution] Proposal: "break for", "break do", "break if", "break case", "break repeat", etc.   Austin Zheng
• [swift-evolution] Proposal: An Either Type in the STL   Ilias Karim
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Amir Michail
• [swift-evolution] Proposal: An Either Type in the STL   Jacob Bandes-Storch
• [swift-evolution] Proposal: An Either Type in the STL   Developer
• [swift-evolution] Proposal: An Either Type in the STL   Dave DeLong
• [swift-evolution] Proposal: Do not allow redundant unwrapping.   Joe Groff
• [swift-evolution] Proposal: An Either Type in the STL   Jacob Bandes-Storch
• [swift-evolution] Proposal: An Either Type in the STL   Ilias Karim
• [swift-evolution] Proposal: An Either Type in the STL   Guillaume Lessard
• [swift-evolution] Remove default case in switch-case   Chris Lattner
• [swift-evolution] Proposal: An Either Type in the STL   Developer
• [swift-evolution] Remove forEach?   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   Jacob Bandes-Storch
• [swift-evolution] Proposal: An Either Type in the STL   Developer
• [swift-evolution] Proposal: Stored properties for enums   Ilias Karim
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   adrian.zubarev at devandartist.com
• [swift-evolution] Proposal: An Either Type in the STL   T.J. Usiyan
• [swift-evolution] Proposal: Stored properties for enums   Frederick Kellison-Linn
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] Remove default case in switch-case   Erica Sadun
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] Proposal: Stored properties for enums   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Chris Lattner
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Jacob Bandes-Storch
• [swift-evolution] List of all Enum values (for simple enums)   Chris Lattner
• [swift-evolution] List of all Enum values (for simple enums)   Jacob Bandes-Storch
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   David Farler
• [swift-evolution] List of all Enum values (for simple enums)   Chris Lattner
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Jordan Rose
• [swift-evolution] Proposal: Change Obj-C name for nested types to include enclosing types   Jordan Rose
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   Stephen Canon
• [swift-evolution] Remove default case in switch-case   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal: Stored properties for enums   Matthew Johnson
• [swift-evolution] Remove default case in switch-case   Casey Cady
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] access control proposal   John McCall
• [swift-evolution] List of all Enum values (for simple enums)   Kevin Wooten
• [swift-evolution] Proposal: Require explicit modifier for statically dispatched extension methods (was: Universal dynamic dispatch for method calls)   Paul Cantrell
• [swift-evolution] Proposal: Change Obj-C name for nested types to include enclosing types   Kevin Ballard
• [swift-evolution] User Defined Attributes/Annotations   Akiva Leffert
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] Proposal: Add @noescape to the transform parameter of 'SequenceType.flatMap'   Dmitri Gribenko
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   Kevin Ballard
• [swift-evolution] Review: SE-0007 (Remove C-style for-loops with conditions and incrementers)   thorsten at portableinnovations.de
• [swift-evolution] User Defined Attributes/Annotations   Tommy van der Vorst
• [swift-evolution] [swift-corelibs-dev] Proposal: Conforming NSDate to Comparable   Chris Amanse
• [swift-evolution] Proposal: An Either Type in the STL   Kevin Ballard
• [swift-evolution] Enforcing guidelines   Steven Van Impe
• [swift-evolution] Proposal: Require explicit modifier for statically dispatched extension methods (was: Universal dynamic dispatch for method calls)   Brent Royal-Gordon
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] Proposal: Stored properties for enums   Al Skipp
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] Extending the for loop to have multiple clauses   thorsten at portableinnovations.de
• [swift-evolution] Extending the for loop to have multiple clauses   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Amir Michail
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   James Campbell
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Kevin Wooten
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Amir Michail
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Adrian Kashivskyy
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Amir Michail
• [swift-evolution] Proposal: Stored properties for enums   Al Skipp
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Kevin Wooten
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Extend CG(Rect)Geometry with center methods   D. Felipe Torres
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Amir Michail
• [swift-evolution] Proposal: Stored properties for enums   Tommy van der Vorst
• [swift-evolution] Proposal: Stored properties for enums   Jonathan Hise Kaldma
• [swift-evolution] Remove forEach?   thorsten at portableinnovations.de
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Harlan Haskins
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Remove forEach?   thorsten at portableinnovations.de
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   plx
• [swift-evolution] Remove forEach?   Chris Eidhof
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Kevin Wooten
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   plx
• [swift-evolution] repeat loop enhancement   thorsten at portableinnovations.de
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Kevin Wooten
• [swift-evolution] swift for ios?   Victor Hugo S Nunes
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   plx
• [swift-evolution] Extending the for loop to have multiple clauses   Chris Eidhof
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Proposal: Extend unnamed let variable scope   Jason Pollack
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Chris Eidhof
• [swift-evolution] Proposal: Extend unnamed let variable scope   Joe Groff
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Joe Groff
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Joe Groff
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Chris Eidhof
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Joe Groff
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Chris Eidhof
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   thorsten at portableinnovations.de
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Andrew Trick
• [swift-evolution] Proposal: Implement == and < for tuples where possible, up to some high arity   plx
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Greg Titus
• [swift-evolution] Proposal: An Either Type in the STL   Nick Shelley
• [swift-evolution] Unify `static` and `class` keywords   Jordan Rose
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Al Skipp
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Douglas Gregor
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   thorsten at portableinnovations.de
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Al Skipp
• [swift-evolution] access control proposal   Drew Crawford
• [swift-evolution] Proposal: An Either Type in the STL   Donnacha Oisín Kidney
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Austin Zheng
• [swift-evolution] Proposal: String literal suffixes for defining types   Kevin Ballard
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Evan Maloney
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Kevin Ballard
• [swift-evolution] Swift source code formatting tool like clang-format for objective-c   Håkon Bogen
• [swift-evolution] User Defined Attributes/Annotations   Rudolf Adamkovic
• [swift-evolution] Proposal: Replace labels with keywords and "*" suffixes   Austin Zheng
• [swift-evolution] Swift source code formatting tool like clang-format for objective-c   Douglas Gregor
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Chris Eidhof
• [swift-evolution] Proposal: An Either Type in the STL   Kevin Ballard
• [swift-evolution] Mailman?   Jacob Bandes-Storch
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Mailman?   Jacob Bandes-Storch
• [swift-evolution] Mailman?   Liam Butler-Lawrence
• [swift-evolution] Proposal Review Schedules   Tyler Cloutier
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] Remove default case in switch-case   Rudolf Adamkovic
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Dmitri Gribenko
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Stephen Celis
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   Denis Nikitenko
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Proposal: An Either Type in the STL   Nick Shelley
• [swift-evolution] Proposal: An Either Type in the STL   plx
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Johan Jensen
• [swift-evolution] Remove isUniquelyReferenced or isUniquelyReferencedNonObjC?   Dmitri Gribenko
• [swift-evolution] Proposal: Allow class cluster pattern via dynamic initializer return type   Riley Testut
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Mailman?   Liam Butler-Lawrence
• [swift-evolution] List of all Enum values (for simple enums)   Joe Groff
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Guillaume Lessard
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Michał Kałużny
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Brent Royal-Gordon
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Evan Maloney
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Douglas Gregor
• [swift-evolution] Review: SE-0007 (Remove C-style for-loops with conditions and incrementers)   thorsten at portableinnovations.de
• [swift-evolution] Protocol declaration inside a class   Виктор Шаманов
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Douglas Gregor
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Mailman?   Douglas Gregor
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Josh Avant
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Paul Cantrell
• [swift-evolution] Warning when "overriding" an extension method that's not in the protocol?   Chris Eidhof
• [swift-evolution] multi-line string literals   Tal Atlas
• [swift-evolution] Proposal: Weak Native Swift Containers   Riley Testut
• [swift-evolution] Make non-void functions @warn_unused_result by default   Adrian Kashivskyy
• [swift-evolution] Proposal: Weak Native Swift Containers   Tommy van der Vorst
• [swift-evolution] Proposal Review Schedules   Douglas Gregor
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] Warning when "overriding" an extension method that's not in the protocol?   Brent Royal-Gordon
• [swift-evolution] Mailman?   Daniel Vollmer
• [swift-evolution] Make non-void functions @warn_unused_result by default   Guillaume Lessard
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   plx
• [swift-evolution] Make non-void functions @warn_unused_result by default   Matthew Johnson
• [swift-evolution] Make non-void functions @warn_unused_result by default   Adrian Kashivskyy
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Al Skipp
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Joe Groff
• [swift-evolution] Proposal: Weak Native Swift Containers   Riley Testut
• [swift-evolution] Make non-void functions @warn_unused_result by default   Riley Testut
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Frederick Kellison-Linn
• [swift-evolution] Mailman?   Jacob Bandes-Storch
• [swift-evolution] Swift 3 Generics   Matthew Johnson
• [swift-evolution] Mailman?   Greg Parker
• [swift-evolution] Make non-void functions @warn_unused_result by default   Joe Groff
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Kevin Ballard
• [swift-evolution] Make non-void functions @warn_unused_result by default   Matthew Johnson
• [swift-evolution] Proposal: Weak Native Swift Containers   John McCall
• [swift-evolution] Foundation and value types   Matthew Johnson
• [swift-evolution] Proposal Review Schedules   Tyler Cloutier
• [swift-evolution] Swift 3 Generics   Austin Zheng
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   David Waite
• [swift-evolution] Swift 3 Generics   Dmitri Gribenko
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Waite
• [swift-evolution] Proposal: Weak Native Swift Containers   Dmitri Gribenko
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] Foundation and value types   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Mailman?   Riley Testut
• [swift-evolution] Make non-void functions @warn_unused_result by default   Adrian Kashivskyy
• [swift-evolution] Proposal: Change Obj-C name for nested types to include enclosing types   Jordan Rose
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Proposal: Weak Native Swift Containers   Greg Parker
• [swift-evolution] Mailman?   Andrey Tarantsov
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Foundation and value types   Tony Parker
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Jordan Rose
• [swift-evolution] Foundation and value types   Dmitri Gribenko
• [swift-evolution] Unify `static` and `class` keywords   Jordan Rose
• [swift-evolution] Proposal: Weak Native Swift Containers   Riley Testut
• [swift-evolution] multi-line string literals   Casey Cady
• [swift-evolution] Foundation and value types   Philippe Hausler
• [swift-evolution] Make non-void functions @warn_unused_result by default   Adrian Kashivskyy
• [swift-evolution] multi-line string literals   Casey Cady
• [swift-evolution] fcntl() should be added to the standard library.   Ted Kremenek
• [swift-evolution] [swift-evolution-announce] [Review] Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] Foundation and value types   Tony Parker
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   J. Cheyo Jimenez
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Joe Groff
• [swift-evolution] Foundation and value types   Dmitri Gribenko
• [swift-evolution] Proposal: Weak Native Swift Containers   Chris Lattner
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] multi-line string literals   Chris Lattner
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] multi-line string literals   Casey Cady
• [swift-evolution] Proposal: Weak Native Swift Containers   Riley Testut
• [swift-evolution] Unify `static` and `class` keywords   Ling Wang
• [swift-evolution] Foundation and value types   David Smith
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Equality of optional arrays   Jake Heiser
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Feijian Sun
• [swift-evolution] Equality of optional arrays   Javier Soto
• [swift-evolution] Making protocol conformance inheritance controllable   Joe Groff
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"‏   Feijian Sun
• [swift-evolution] Proposal: An Either Type in the STL   John McCall
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"‏   Jack Lawrence
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"‏   Feijian Sun
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Seth Friedman
• [swift-evolution] Making protocol conformance inheritance controllable   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Feijian Sun
• [swift-evolution] User Defined Attributes/Annotations   Akiva Leffert
• [swift-evolution] fcntl() should be added to the standard library.   Bill Abt
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   David Owens II
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Seth Friedman
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Feijian Sun
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Frederick Kellison-Linn
• [swift-evolution] Making protocol conformance inheritance controllable   Michel Fortin
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   John McCall
• [swift-evolution] Proposal: Change Obj-C name for nested types to include enclosing types   Kevin Ballard
• [swift-evolution] Protocol declaration inside a class   Slava Pestov
• [swift-evolution] Swift 3 Generics   Slava Pestov
• [swift-evolution] List of all Enum values (for simple enums)   Slava Pestov
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Slava Pestov
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Evan Maloney
• [swift-evolution] multi-line string literals   Chris Lattner
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Michael Buckley
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"‏   Chris Lattner
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Kevin Wooten
• [swift-evolution] User Defined Attributes/Annotations   Chris Lattner
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Paul Cantrell
• [swift-evolution] Proposal: Add Initializers For Converting UnsafePointers to Int and Unit   Dmitri Gribenko
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Chris Lattner
• [swift-evolution] Making protocol conformance inheritance controllable   Chris Lattner
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Making protocol conformance inheritance controllable   T.J. Usiyan
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Chris Lattner
• [swift-evolution] Making protocol conformance inheritance controllable   Evan Maloney
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Greg Parker
• [swift-evolution] Allowing non-binding pattern matching as a Bool expression?   Chris Lattner
• [swift-evolution] multi-line string literals   Paul Cantrell
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Chris Lattner
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] multi-line string literals   Paul Cantrell
• [swift-evolution] Proposal: String literal suffixes for defining types   Chris Lattner
• [swift-evolution] Enforcing guidelines   Chris Lattner
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   Chris Lattner
• [swift-evolution] Polymorphic behavior for overloaded == (and other) operators   Chris Lattner
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   Chris Lattner
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] Make non-void functions @warn_unused_result by default   Kametrixom Tikara
• [swift-evolution] Proposal: Extend CG(Rect)Geometry with center methods   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Brent Royal-Gordon
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   David Farler
• [swift-evolution] multi-line string literals   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] User Defined Attributes/Annotations   Bryan Irace
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   Chris Lattner
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Drew Crawford
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Chris Lattner
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Unmanaged, and COpaquePointer vs. Unsafe(Mutable)Pointer   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Making protocol conformance inheritance controllable   thorsten at portableinnovations.de
• [swift-evolution] Inheritance with a Constrain   Douglas Gregor
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   thorsten at portableinnovations.de
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] Mailman?   Pierre Monod-Broca
• [swift-evolution] Mailman?   Pierre Monod-Broca
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] multi-line string literals   David Owens II
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Gwendal Roué
• [swift-evolution] Enforcing guidelines   Brent Royal-Gordon
• [swift-evolution] Swift source code formatting tool like clang-format for objective-c   Håkon Bogen
• [swift-evolution] Closure delegation   Pierre Monod-Broca
• [swift-evolution] Proposal: Namespaces   T.J. Usiyan
• [swift-evolution] Swift source code formatting tool like clang-format for objective-c   James Campbell
• [swift-evolution] Making protocol conformance inheritance controllable   Gwendal Roué
• [swift-evolution] Closure delegation   James Campbell
• [swift-evolution] Proposal: Namespaces   James Campbell
• [swift-evolution] multi-line string literals   Drew Crawford
• [swift-evolution] multi-line string literals   Drew Crawford
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Waite
• [swift-evolution] Closure delegation   Pierre Monod-Broca
• [swift-evolution] Closure delegation   James Campbell
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   ilya
• [swift-evolution] multi-line string literals   Marc Knaup
• [swift-evolution] Closure delegation   Marc Knaup
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"‏   Feijian Sun
• [swift-evolution] Closure delegation   Pierre Monod-Broca
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Al Skipp
• [swift-evolution] Remove default case in switch-case   Jeremy Pereira
• [swift-evolution] Proposal: "inout" in for loops   Amir Michail
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Sandy Chapman
• [swift-evolution] Making protocol conformance inheritance controllable   Matthew Johnson
• [swift-evolution] Proposal for Replacing Keyword "subscript" with "subs"   Feijian Sun
• [swift-evolution] Closure delegation   Matthew Johnson
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Al Skipp
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Brent Royal-Gordon
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Brent Royal-Gordon
• [swift-evolution] Closure delegation   James Campbell
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Making protocol conformance inheritance controllable   plx
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Paul Cantrell
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Paul Cantrell
• [swift-evolution] Equality of enum with payload   Jérôme Duquennoy
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Daniel Hooper
• [swift-evolution] Equality of enum with payload   Marc Knaup
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Jeff Kelley
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Erica Sadun
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Marc Knaup
• [swift-evolution] Equality of enum with payload   Slava Pestov
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Sean Heber
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Stephen Canon
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Erica Sadun
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Marc Knaup
• [swift-evolution] multi-line string literals   David Owens II
• [swift-evolution] (no subject)   John Siracusa
• [swift-evolution] multi-line string literals   Marc Knaup
• [swift-evolution] Proposal: Add Flags to Disable [Optional] Conversions   Kenny Leung
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   ilya
• [swift-evolution] Polymorphic behavior for overloaded == (and other) operators   Frederick Kellison-Linn
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] multi-line string literals   John Siracusa
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Sean Heber
• [swift-evolution] Method cascading (was Re: Request for Discussion: Setup closures)   Kenny Leung
• [swift-evolution] Equality of enum with payload   Jonathan Hise Kaldma
• [swift-evolution] [swift-evolution-announce] [Review] Remove C-style for-loops with conditions and incrementers   Joe Groff
• [swift-evolution] Closure delegation   ilya
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Wallacy
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Stephen Canon
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Daniel Hooper
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Marc Knaup
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Josh Avant
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   ilya
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Marc Knaup
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Al Skipp
• [swift-evolution] Proposal Sketch: simplify optional unwrapping syntax   Daniel Hooper
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Gwendal Roué
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Jordan Rose
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   David Owens II
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   inbox only
• [swift-evolution] [swift-evolution-announce] [Review] Remove C-style for-loops with conditions and incrementers   Nadav Rotem
• [swift-evolution] Swift 2.2: Removing partial application of super method calls   Slava Pestov
• [swift-evolution] Proposal: Auto-implemented computed properties   Nathan Yee
• [swift-evolution] Proposal: Auto-implemented computed properties   Nicky Gerritsen
• [swift-evolution] Proposal: Auto-implemented computed properties   Chris Lattner
• [swift-evolution] [Review] Remove C-style for-loops with conditions and incrementers   Douglas Gregor
• [swift-evolution] Polymorphic behavior for overloaded == (and other) operators   Chris Lattner
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Slava Pestov
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   James Campbell
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Gwendal Roué
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Slava Pestov
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Gwendal Roué
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Tyler Cloutier
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Gwendal Roué
• [swift-evolution] Proposal: newtype feature for creating brand new types from existing types   tuuranton at tutanota.de
• [swift-evolution] Proposal: Auto-implemented computed properties   Stephen Celis
• [swift-evolution] Making protocol conformance inheritance controllable   Joe Groff
• [swift-evolution] Proposal: newtype feature for creating brand new types from existing types   Gwendal Roué
• [swift-evolution] Proposal: newtype feature for creating brand new types from existing types   Nicky Gerritsen
• [swift-evolution] Proposal: newtype feature for creating brand new types from existing types   Alejandro Martinez
• [swift-evolution] Proposal: newtype feature for creating brand new types from existing types   Alejandro Martinez
• [swift-evolution] Request: Ability to refer to an enum case in abstract (without its associated value)   Evan Maloney
• [swift-evolution] Making protocol conformance inheritance controllable   Michel Fortin
• [swift-evolution] Equality of enum with payload   Marc Knaup
• [swift-evolution] Enforcing guidelines   Douglas Gregor
• [swift-evolution] Proposal: Extend CG(Rect)Geometry with center methods   D. Felipe Torres
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Enforcing guidelines   Jason Dusek
• [swift-evolution] Proposal: String literal suffixes for defining types   Kevin Ballard
• [swift-evolution] multi-line string literals   Drew Crawford
• [swift-evolution] Object declarations   Marc Knaup
• [swift-evolution] multi-line string literals   Brent Royal-Gordon
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Josh Avant
• [swift-evolution] Object declarations   Thorsten Seitz
• [swift-evolution] Object declarations   Marc Knaup
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Object declarations   Thorsten Seitz
• [swift-evolution] multi-line string literals   Marc Knaup
• [swift-evolution] Proposal: String literal suffixes for defining types   Joe Groff
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Douglas Gregor
• [swift-evolution] Object declarations   Marc Knaup
• [swift-evolution] Proposal: String literal suffixes for defining types   Marc Knaup
• [swift-evolution] Object declarations   Thorsten Seitz
• [swift-evolution] multi-line string literals   Brent Royal-Gordon
• [swift-evolution] Object declarations   Jordan Rose
• [swift-evolution] multi-line string literals   Kametrixom Tikara
• [swift-evolution] Object declarations   Kevin Lundberg
• [swift-evolution] Object declarations   Brent Royal-Gordon
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] union types   Drew Crawford
• [swift-evolution] Make non-void functions @warn_unused_result by default   Douglas Gregor
• [swift-evolution] multi-line string literals   Drew Crawford
• [swift-evolution] multi-line string literals   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Kametrixom Tikara
• [swift-evolution] Warning when "overriding" an extension method that's not in the protocol?   Douglas Gregor
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Make non-void functions @warn_unused_result by default   Marc Knaup
• [swift-evolution] List of all Enum values (for simple enums)   Zef Houssney
• [swift-evolution] union types   Dmitri Gribenko
• [swift-evolution] multi-line string literals   Kametrixom Tikara
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Object declarations   Riley Avron
• [swift-evolution] multi-line string literals   Marc Knaup
• [swift-evolution] union types   Drew Crawford
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] Proposal: Add generator functions to the language   Drew Crawford
• [swift-evolution] Proposal: Add generator functions to the language   Jacob Bandes-Storch
• [swift-evolution] multi-line string literals   Jason Dusek
• [swift-evolution] List of all Enum values (for simple enums)   Brent Royal-Gordon
• [swift-evolution] Object declarations   Jérôme Duquennoy
• [swift-evolution] multi-line string literals   Kametrixom Tikara
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] multi-line string literals   Kametrixom Tikara
• [swift-evolution] ternary operator ?: suggestion   Andrew Brown
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Andrey Tarantsov
• [swift-evolution] ternary operator ?: suggestion   Andrey Tarantsov
• [swift-evolution] Object declarations   Andrey Tarantsov
• [swift-evolution] ternary operator ?: suggestion   Drew Crawford
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] ternary operator ?: suggestion   Andrey Tarantsov
• [swift-evolution] Proposal: Add generator functions to the language   Kametrixom Tikara
• [swift-evolution] Proposal: Add generator functions to the language   Drew Crawford
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] Object declarations   Marc Knaup
• [swift-evolution] List of all Enum values (for simple enums)   Zef Houssney
• [swift-evolution] Proposal: Add generator functions to the language   Kevin Wooten
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] multi-line string literals   Andrey Tarantsov
• [swift-evolution] ternary operator ?: suggestion   Andrey Tarantsov
• [swift-evolution] Proposal: Add generator functions to the language   Kametrixom Tikara
• [swift-evolution] Proposal: Add generator functions to the language   Andrey Tarantsov
• [swift-evolution] Proposal: Add generator functions to the language   Greg Parker
• [swift-evolution] do try catch?   Liam Butler-Lawrence
• [swift-evolution] Proposal: Add generator functions to the language   Andrey Tarantsov
• [swift-evolution] Proposal: Add generator functions to the language   Jordan Rose
• [swift-evolution] Proposal: Add generator functions to the language   Jordan Rose
• [swift-evolution] Proposal: Add generator functions to the language   Andrey Tarantsov
• [swift-evolution] Proposal: Add generator functions to the language   Jordan Rose
• [swift-evolution] Proposal: Add generator functions to the language   Jonathan Hise Kaldma
• [swift-evolution] Proposal: Add generator functions to the language   Jordan Rose
• [swift-evolution] do try catch?   John McCall
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] Proposal: Intermediate mutation qualifier for protocol functions on reference-types   Chris Lattner
• [swift-evolution] union types   Joe Groff
• [swift-evolution] Proposal: Add generator functions to the language   Joe Groff
• [swift-evolution] Proposal: Add generator functions to the language   Alex Gordon
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] union types   Drew Crawford
• [swift-evolution] access control proposal   Ilya
• [swift-evolution] union types   Joe Groff
• [swift-evolution] Proposal: An Either Type in the STL   Developer
• [swift-evolution] do try catch?   Liam Butler-Lawrence
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] (no subject)   Chris Lattner
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Kevin Ballard
• [swift-evolution] ternary operator ?: suggestion   Chris Lattner
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Douglas Gregor
• [swift-evolution] Proposal: Add generator functions to the language   Kevin Wooten
• [swift-evolution] Swift 3 Generics   Douglas Gregor
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Douglas Gregor
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: Require explicit modifier for statically dispatched extension methods (was: Universal dynamic dispatch for method calls)   Kevin Ballard
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Kevin Ballard
• [swift-evolution] Proposal: An Either Type in the STL   Kevin Ballard
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Sabintsev
• [swift-evolution] Proposal: Add generator functions to the language   Kevin Ballard
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Kevin Ballard
• [swift-evolution] Proposal: Auto-convert for numbers when safe   Douglas Gregor
• [swift-evolution] multi-line string literals   Alex Gordon
• [swift-evolution] Make non-void functions @warn_unused_result by default   Kevin Ballard
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Ariel Sabintsev
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Kevin Ballard
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Ariel Sabintsev
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Chris Lattner
• [swift-evolution] multi-line string literals   Travis Tilley
• [swift-evolution] Proposal: "inout" in for loops   Chris Lattner
• [swift-evolution] Proposal: Auto-convert for numbers when safe   Manav Gabhawala
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Kevin Ballard
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Proposal: An Either Type in the STL   T.J. Usiyan
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Marc Knaup
• [swift-evolution] Proposal: Add generator functions to the language   ilya
• [swift-evolution] Proposal: Add generator functions to the language   T.J. Usiyan
• [swift-evolution] Proposal: String literal suffixes for defining types   ilya
• [swift-evolution] Is there a need for a BigNumber library in Objective-C/Swift?   Otto van Verseveld
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] ternary operator ?: suggestion   Thorsten Seitz
• [swift-evolution] Proposal: Add generator functions to the language   Andrew Bennett
• [swift-evolution] ternary operator ?: suggestion   Andrew Brown
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Andrew Brown
• [swift-evolution] Proposal: String literal suffixes for defining types   Michel Fortin
• [swift-evolution] union types   David Hart
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Stephen Celis
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Amir Michail
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Marc Knaup
• [swift-evolution] access control proposal   Brent Royal-Gordon
• [swift-evolution] Add unless/if single line syntax   James Campbell
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Al Skipp
• [swift-evolution] Should we consider Swift improvements for indie solo programmers?   Amir Michail
• [swift-evolution] Should we consider Swift improvements for indie solo programmers?   Marc Knaup
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Rainer Brockerhoff
• [swift-evolution] Add unless/if single line syntax   J. Cheyo Jimenez
• [swift-evolution] Should we consider Swift improvements for indie solo programmers?   Al Skipp
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Matthew Johnson
• [swift-evolution] Add unless/if single line syntax   Arthur Ariel Sabintsev
• [swift-evolution] Add unless/if single line syntax   Matthew Johnson
• [swift-evolution] Add unless/if single line syntax   Al Skipp
• [swift-evolution] Add unless/if single line syntax   Matthew Johnson
• [swift-evolution] Add unless/if single line syntax   James Campbell
• [swift-evolution] Should we consider Swift improvements for indie solo programmers?   Amir Michail
• [swift-evolution] Add unless/if single line syntax   Tommy van der Vorst
• [swift-evolution] Add unless/if single line syntax   Tommy van der Vorst
• [swift-evolution] Add unless/if single line syntax   Al Skipp
• [swift-evolution] Add unless/if single line syntax   Matthew Johnson
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Add unless/if single line syntax   Amir Michail
• [swift-evolution] Explicit Protocol Conformance for Child Classes   Arthur Ariel Sabintsev
• [swift-evolution] Add unless/if single line syntax   James Campbell
• [swift-evolution] Should we consider Swift improvements for indie solo programmers?   Al Skipp
• [swift-evolution] union types   Matthew Johnson
• [swift-evolution] More flexible guard statement   Jakob Egger
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] More flexible guard statement   Arthur Sabintsev
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Rainer Brockerhoff
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Rainer Brockerhoff
• [swift-evolution] More flexible guard statement   Al Skipp
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] [Review] SE-0007 Remove C-style for-loops with conditions and incrementers   Brent Royal-Gordon
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Rainer Brockerhoff
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Matthew Johnson
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Sabintsev
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] Proposal: An Either Type in the STL   Joe Groff
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   David Waite
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Michel Fortin
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Sabintsev
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Joe Groff
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Andrey Tarantsov
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Arthur Sabintsev
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Douglas Gregor
• [swift-evolution] Proposal: An Either Type in the STL   Matthew Johnson
• [swift-evolution] Proposal: Add generator functions to the language   Douglas Gregor
• [swift-evolution] ternary operator ?: suggestion   Andrey Tarantsov
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: Auto-convert for numbers when safe   Douglas Gregor
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Jérôme Duquennoy
• [swift-evolution] More flexible guard statement   Zef Houssney
• [swift-evolution] Proposal: Allow @objc(name) on enum declarations   Douglas Gregor
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: String literal suffixes for defining types   Kevin Ballard
• [swift-evolution] Optional "endfor", "endif", etc after closing "}"   Greg Parker
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] Add unless/if single line syntax   Jason Dusek
• [swift-evolution] SR-104: Improve Crash-Safety when Importing Objective-C Code Without Nullability Attributes   Fabian Ehrentraud
• [swift-evolution] access control proposal   Drew Crawford
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Review for: Remove C-style for-loops with conditions and incrementers   Rainer Brockerhoff
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Slava Pestov
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] access control proposal   Ilya Belenkiy
• [swift-evolution] Remove forEach?   Michael Henson
• [swift-evolution] ternary operator ?: suggestion   Daniel Valls Estella
• [swift-evolution] Proposal: conversion protocol naming conventions   Matthew Johnson
• [swift-evolution] Proposal: conversion protocol naming conventions   Arthur Sabintsev
• [swift-evolution] Proposal: conversion protocol naming conventions   Matthew Johnson
• [swift-evolution] Proposal: allow delegating from a throwing initializer to a failable initializer   Matthew Johnson
• [swift-evolution] Streamlining closures   Taras Zakharko
• [swift-evolution] Proposal: Add generator functions to the language   Alex Gordon
• [swift-evolution] Proposal: Add generator functions to the language   Taras Zakharko
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Making protocol conformance inheritance controllable   Nate Cook
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Rob Napier
• [swift-evolution] Streamlining closures   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: An Either Type in the STL   Thorsten Seitz
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   ilya
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   ilya
• [swift-evolution] Language or XCTest improvements to allow testing assert/precondition failures   David Hart
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] Proposal: Implement a rotate algorithm, equivalent to std::rotate() in C++   Sergey Bolshedvorsky
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   ilya
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] Proposal: label-only constructors   Drew Crawford
• [swift-evolution] Proposal: label-only constructors   ilya
• [swift-evolution] Proposal: label-only constructors   Drew Crawford
• [swift-evolution] Proposal: label-only constructors   ilya
• [swift-evolution] Proposal: label-only constructors   Drew Crawford
• [swift-evolution] Proposal: label-only constructors   Marc Knaup
• [swift-evolution] ternary operator ?: suggestion   Matthew Johnson
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Marc Knaup
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] Proposal to remove semicolons   João Nunes
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] Language or XCTest improvements to allow testing assert/precondition failures   Marc Knaup
• [swift-evolution] Streamlining closures   Marc Knaup
• [swift-evolution] Streamlining closures   Taras Zakharko
• [swift-evolution] ternary operator ?: suggestion   Thorsten Seitz
• [swift-evolution] Streamlining closures   Thorsten Seitz
• [swift-evolution] ternary operator ?: suggestion   Thorsten Seitz
• [swift-evolution] ternary operator ?: suggestion   Taras Zakharko
• [swift-evolution] Streamlining closures   Marc Knaup
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   ilya
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Marc Knaup
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] Proposal: label-only constructors   ilya
• [swift-evolution] ternary operator ?: suggestion   Jakob Egger
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Al Skipp
• [swift-evolution] ternary operator ?: suggestion   Taras Zakharko
• [swift-evolution] Proposal: label-only constructors   Sean Heber
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: label-only constructors   Harlan Haskins
• [swift-evolution] ternary operator ?: suggestion   Al Skipp
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Language or XCTest improvements to allow testing assert/precondition failures   Daniel Dunbar
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: Add generator functions to the language   David Waite
• [swift-evolution] ternary operator ?: suggestion   Dennis Lysenko
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Waite
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Dennis Lysenko
• [swift-evolution] ternary operator ?: suggestion   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   ilya
• [swift-evolution] Proposal: Add generator functions to the language   Alex Gordon
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] Proposal: willGet   Paul Cantrell
• [swift-evolution] ternary operator ?: suggestion   Andrew Brown
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Streamlining closures   Andrew Brown
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
• [swift-evolution] Proposal: label-only constructors   David Owens II
• [swift-evolution] ternary operator ?: suggestion   Paul Ossenbruggen
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Chris Lattner
• [swift-evolution] Proposal: willGet   Chris Lattner
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Charles Srstka
• [swift-evolution] ASCIIString   Jacob Bandes-Storch
• [swift-evolution] Proposal: willGet   Paul Cantrell
• [swift-evolution] Proposal: willGet   Chris Lattner
• [swift-evolution] Proposal: Extend CG(Rect)Geometry with center methods   Jacob Bandes-Storch
• [swift-evolution] Proposal: label-only constructors   Drew Crawford
• [swift-evolution] access control proposal   Brent Royal-Gordon
• [swift-evolution] ASCIIString   Paul Cantrell
• [swift-evolution] ASCIIString   Austin Zheng
• [swift-evolution] Proposal: Extend CG(Rect)Geometry with center methods   Marc Knaup
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Andrew Brown
• [swift-evolution] Explicit Protocol Conformance for Child Classes   Jacob Bandes-Storch
• [swift-evolution] Proposal: Add replace(_:with:) function to the stdlib   Kevin Ballard
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Chris Lattner
• [swift-evolution] Proposal: Add generator functions to the language   Chris Lattner
• [swift-evolution] Proposal: willGet   Andrew Bennett
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Chris Lattner
• [swift-evolution] Proposal: label-only constructors   Jason Dusek
• [swift-evolution] Run Swift code at compile time   Andrew Brown
• [swift-evolution] Explicit Protocol Conformance for Child Classes   Kevin Ballard
• [swift-evolution] access control proposal   Drew Crawford
• [swift-evolution] Proposal: Allow for/in to take GeneratorType in addition to SequenceType   Michael Henson
• [swift-evolution] Proposal: Namespaces   Cole Kurkowski
• [swift-evolution] Proposal: Namespaces   Marc Knaup
• [swift-evolution] access control proposal   Matthew Johnson
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Kevin Ballard
• [swift-evolution] protocol can only be used as a generic constraint because it has Self or associated type requirements   Marc Knaup
• [swift-evolution] Mailman?   Zach Drayer
• [swift-evolution] Proposal: Namespaces   T.J. Usiyan
• [swift-evolution] Object declarations   Cole Kurkowski
• [swift-evolution] Proposal: Allow for/in to take GeneratorType in addition to SequenceType   Dmitri Gribenko
• [swift-evolution] Object declarations   Marc Knaup
• [swift-evolution] Proposal: Expose getter/setters in the same way as regular methods   Michael Henson
• [swift-evolution] Proposal: Expose getter/setters in the same way as regular methods   Marc Knaup
• [swift-evolution] Proposal: Expose getter/setters in the same way as regular methods   Matthew Johnson
• [swift-evolution] Proposal: Namespaces   Cole Kurkowski
• [swift-evolution] Proposal: Namespaces   Marc Knaup
• [swift-evolution] Proposal: Namespaces   Cole Kurkowski
• [swift-evolution] Object declarations   Cole Kurkowski
• [swift-evolution] access control proposal   Brent Royal-Gordon
• [swift-evolution] Proposal: Give weak references the ability to notify reference-holders when they transition to nil   Michael Henson
• [swift-evolution] More flexible guard statement   Jeff Kelley
• [swift-evolution] Proposal: Enclosed variable in extension scope   Nutchaphon Rewik
• [swift-evolution] Proposal: Enclosed variable in extension scope   Matthew Johnson
• [swift-evolution] Proposal for Passing Arrays to Variadic Functions   Chris Lattner
• [swift-evolution] Object declarations   Chris Lattner
• [swift-evolution] Proposal: Give weak references the ability to notify reference-holders when they transition to nil   Chris Lattner
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Dennis Lysenko
• [swift-evolution] Proposal: Give weak references the ability to notify reference-holders when they transition to nil   Paul Cantrell
• [swift-evolution] Proposal: Add replace(_:with:) function to the stdlib   Paul Cantrell
• [swift-evolution] Proposal: Add replace(_:with:) function to the stdlib   Dave Abrahams
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Nick Shelley
• [swift-evolution] Proposal: Universal dynamic dispatch for method calls   Paul Cantrell
• [swift-evolution] Proposal: Allow for/in to take GeneratorType in addition to SequenceType   Dave Abrahams
• [swift-evolution] protocol can only be used as a generic constraint because it has Self or associated type requirements   Dave Abrahams

Last message date: Sun Dec 13 23:56:51 CST 2015
Archived on: Mon Dec 14 11:15:22 CST 2015

• Messages sorted by: [ thread ] [ subject ] [ author ]
• More info on this list...