The Week Of Monday 29 February 2016 Archives by subject

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

Starting: Mon Feb 29 00:24:42 CST 2016
Ending: Sun Mar 6 23:19:20 CST 2016
Messages: 573

• [swift-evolution] .stride with real (floating point) number ranges   ted van gaalen
• [swift-evolution] .stride: using real ( floating point) number ranges   Dany St-Amant
• [swift-evolution] .stride: using real ( floating point) number ranges   Ted van Gaalen
• [swift-evolution] [Accepted with modification] SE-0005 "Better Translation of Objective-C APIs Into Swift"   Douglas Gregor
• [swift-evolution] [Accepted with modification] SE-0005 "Better Translation of Objective-C APIs Into Swift"   Radosław Pietruszewski
• [swift-evolution] [Accepted with modification] SE-0005 "Better Translation of Objective-C APIs Into Swift"   Ben Rimmington
• [swift-evolution] [Accepted with modification] SE-0005 "Better Translation of Objective-C APIs Into Swift"   Howard Lovatt
• [swift-evolution] [Accepted with modifications] SE-0006 "Apply API Guidelines to the Standard Library"   Douglas Gregor
• [swift-evolution] [Accepted with modifications] SE-0023 API Design Guidelines   Douglas Gregor
• [swift-evolution] [Administrative] Update proposals with Accepted/Rejected status   Kenny Leung
• [swift-evolution] [Administrative] Update proposals with Accepted/Rejected status   Chris Lattner
• [swift-evolution] [Completing Generics] Any<> syntax, base class constraints, and existential metatypes   Matthew Judge
• [swift-evolution] [Completing Generics] Any<> syntax, base class constraints, and existential metatypes   Joe Groff
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Joe Groff
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Brent Royal-Gordon
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Goffredo Marocchi
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Brent Royal-Gordon
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Goffredo Marocchi
• [swift-evolution] [Completing Generics] Completing protocol extension diagnostics   Haravikk
• [swift-evolution] [Completing Generics] Opening existentials — A use case: type-safe dependency injection container   Adam Sharp
• [swift-evolution] [Completing Generics] Private and multiple conformances   Douglas Gregor
• [swift-evolution] [Completing Generics] Private and multiple conformances   Joe Groff
• [swift-evolution] [Completing Generics] Private and multiple conformances   Douglas Gregor
• [swift-evolution] [Completing Generics] Private and multiple conformances   Joe Groff
• [swift-evolution] [Completing Generics] Private and multiple conformances   Douglas Gregor
• [swift-evolution] [Completing Generics] Private and multiple conformances   Joe Groff
• [swift-evolution] [Completing Generics] Private and multiple conformances   Slava Pestov
• [swift-evolution] [Completing Generics] Universal conformances   Joe Groff
• [swift-evolution] [Completing Generics] Universal conformances   Joe Groff
• [swift-evolution] [Discussion/Draft] Allow Precedence For Prefix And Postfix Operators   Chris Lattner
• [swift-evolution] [Discussion/Draft] Allow Precedence For Prefix And Postfix Operators   Daniel Duan
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Erica Sadun
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   David Owens II
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Charles Kissinger
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Erica Sadun
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Brent Royal-Gordon
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Erica Sadun
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Brent Royal-Gordon
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Charles Kissinger
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Erica Sadun
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Erica Sadun
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Adam Sharp
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Kevin Ballard
• [swift-evolution] [Discussion] Adopting a new common error type outside the bounds of NSError   Kevin Ballard
• [swift-evolution] [Discussion] Enforcing Calling Super   Jeremy Pereira
• [swift-evolution] [Discussion] Enforcing Calling Super   Kyle Sherman
• [swift-evolution] [Discussion] Enforcing Calling Super   Tino Heth
• [swift-evolution] [Discussion] Enforcing Calling Super   Jeremy W. Sherman
• [swift-evolution] [Discussion] Enforcing Calling Super   Kyle Sherman
• [swift-evolution] [Discussion] Enforcing Calling Super   Kyle Sherman
• [swift-evolution] [Discussion] Enforcing Calling Super   Jeremy W. Sherman
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Brent Royal-Gordon
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Radosław Pietruszewski
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Stephen Celis
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Stephen Celis
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Brent Royal-Gordon
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Stephen Celis
• [swift-evolution] [Discussion] Here we go again: Extension Functions   Pierre Monod-Broca
• [swift-evolution] [Discussion] Modernizing Attribute Case and Attribute Argument Naming   Chris Lattner
• [swift-evolution] [Discussion] Modernizing Attribute Case and Attribute Argument Naming   Erica Sadun
• [swift-evolution] [Discussion] Modernizing Attribute Case and Attribute Argument Naming   Dave Abrahams
• [swift-evolution] [Discussion] Referencing the Objective-C selector of property getters and setters   Adrian Kashivskyy
• [swift-evolution] [Discussion] Replacing Equal Signs with Colons For Attribute Arguments   Adrian Kashivskyy
• [swift-evolution] [Discussion] stride behavior and a little bit of a call-back to digital numbers   Erica Sadun
• [swift-evolution] [Discussion] stride behavior and a little bit of a call-back to digital numbers   Erica Sadun
• [swift-evolution] [Discussion] stride behavior and a little bit of a call-back to digital numbers   Joe Groff
• [swift-evolution] [Discussion] stride behavior and a little bit of a call-back to digital numbers   Joe Groff
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Pyry Jahkola
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   davesweeris at mac.com
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Chris Lattner
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Simon Pilkington
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Haravikk
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Brent Royal-Gordon
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Charles Srstka
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Joseph Lord
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Seth Friedman
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Radosław Pietruszewski
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   David Owens II
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Kenny Leung
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Patrick Gili
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Patrick Gili
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Erica Sadun
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Joel Lopes Da Silva
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Jacob Bandes-Storch
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Dave Abrahams
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Dave Abrahams
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Brent Royal-Gordon
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Developer
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Vanderlei Martinelli
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Charles Kissinger
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Pierre Monod-Broca
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Andrey Tarantsov
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   Brent Royal-Gordon
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   marc hoffman
• [swift-evolution] [Discussion]: Deprecate !-Unwrapping of Optionals   William Dillon
• [swift-evolution] [Discussion][Expericment] D-like slicing syntax   Dave Abrahams
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Evan Maloney
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Developer
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Evan Maloney
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Pierre Monod-Broca
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Pierre Monod-Broca
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   David Scrève
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Gwendal Roué
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Evan Maloney
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Pierre Monod-Broca
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Goffredo Marocchi
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Vinicius Vendramini
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Vanderlei Martinelli
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Andrey Tarantsov
• [swift-evolution] [Draft] Allow declaration of abstract functions and properties on classes   Wallacy
• [swift-evolution] [Draft] Conventionalize #setline   Антон Жилин
• [swift-evolution] [Draft] Mixins   Антон Жилин
• [swift-evolution] [Draft] Mixins   Patrick Gili
• [swift-evolution] [Draft] Mixins   David Waite
• [swift-evolution] [Draft] Mixins   Howard Lovatt
• [swift-evolution] [Draft] Mixins   Thorsten Seitz
• [swift-evolution] [Draft] Mixins   Howard Lovatt
• [swift-evolution] [Draft] Mixins   Brian Pratt
• [swift-evolution] [Draft] Mixins   Andrey Tarantsov
• [swift-evolution] [Draft] Mixins   Simon Pilkington
• [swift-evolution] [Draft] Mixins   Thorsten Seitz
• [swift-evolution] [Draft] Mixins   Thorsten Seitz
• [swift-evolution] [Draft] Mixins   Антон Жилин
• [swift-evolution] [Draft] Mixins   Thorsten Seitz
• [swift-evolution] [Draft] Mixins: What present problems do they solve?   Jeremy W. Sherman
• [swift-evolution] [Draft] Mixins: What present problems do they solve?   Matt Whiteside
• [swift-evolution] [Draft] Obejctive-C Keypaths   David Hart
• [swift-evolution] [Draft] Obejctive-C Keypaths   Félix Cloutier
• [swift-evolution] [Draft] Obejctive-C Keypaths   David Hart
• [swift-evolution] [Draft] Obejctive-C Keypaths   Brent Royal-Gordon
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   Dmitri Gribenko
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   Dmitri Gribenko
• [swift-evolution] [Draft] Target-specific CChar   Joe Groff
• [swift-evolution] [Draft] Target-specific CChar   Dmitri Gribenko
• [swift-evolution] [Draft] Target-specific CChar   Dmitri Gribenko
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   Joe Groff
• [swift-evolution] [Draft] Target-specific CChar   Jeremy Pereira
• [swift-evolution] [Draft] Target-specific CChar   Brent Royal-Gordon
• [swift-evolution] [Draft] Target-specific CChar   Ben Rimmington
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   Ben Rimmington
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   William Dillon
• [swift-evolution] [Draft] Target-specific CChar   Michel Fortin
• [swift-evolution] [Idea] Allowing most keywords after "."   Brent Royal-Gordon
• [swift-evolution] [Idea] Allowing most keywords after "."   Chris Lattner
• [swift-evolution] [Manifesto] Completing Generics   Douglas Gregor
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   David Smith
• [swift-evolution] [Manifesto] Completing Generics   Developer
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   David Smith
• [swift-evolution] [Manifesto] Completing Generics   Douglas Gregor
• [swift-evolution] [Manifesto] Completing Generics   Developer
• [swift-evolution] [Manifesto] Completing Generics   Slava Pestov
• [swift-evolution] [Manifesto] Completing Generics   Slava Pestov
• [swift-evolution] [Manifesto] Completing Generics   Douglas Gregor
• [swift-evolution] [Manifesto] Completing Generics   Brent Royal-Gordon
• [swift-evolution] [Manifesto] Completing Generics   Slava Pestov
• [swift-evolution] [Manifesto] Completing Generics   Haravikk
• [swift-evolution] [Manifesto] Completing Generics   plx
• [swift-evolution] [Manifesto] Completing Generics   plx
• [swift-evolution] [Manifesto] Completing Generics   plx
• [swift-evolution] [Manifesto] Completing Generics   Joe Groff
• [swift-evolution] [Manifesto] Completing Generics   Dave Abrahams
• [swift-evolution] [Manifesto] Completing Generics   Dave Abrahams
• [swift-evolution] [Manifesto] Completing Generics   Brent Royal-Gordon
• [swift-evolution] [Manifesto] Completing Generics   Thorsten Seitz
• [swift-evolution] [Manifesto] Completing Generics   Dave Abrahams
• [swift-evolution] [META] Re: Mailman?   Erica Sadun
• [swift-evolution] [META] Re: Mailman?   Radosław Pietruszewski
• [swift-evolution] [META] Re: Mailman?   Goffredo Marocchi
• [swift-evolution] [META] Re: Mailman?   Kevin Lundberg
• [swift-evolution] [META] Re: Mailman?   Fload
• [swift-evolution] [META] Re: Mailman?   James Campbell
• [swift-evolution] [META] Re: Mailman?   Dennis Lysenko
• [swift-evolution] [Pitch] Instance var/let property as type member could be unbound function   Tikitu de Jager
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Howard Lovatt
• [swift-evolution] [Pitch] Move @noescape   Félix Cloutier
• [swift-evolution] [Pitch] Move @noescape   Jacob Bandes-Storch
• [swift-evolution] [Pitch] Move @noescape   Jacob Bandes-Storch
• [swift-evolution] [Pitch] Move @noescape   Brent Royal-Gordon
• [swift-evolution] [Pitch] Move @noescape   Brent Royal-Gordon
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Brent Royal-Gordon
• [swift-evolution] [Pitch] Move @noescape   Chris Lattner
• [swift-evolution] [Pitch] Move @noescape   Howard Lovatt
• [swift-evolution] [Proposal draft] Import as member   Michael Ilseman
• [swift-evolution] [Proposal draft] Import as member   Jeff Kelley
• [swift-evolution] [Proposal draft] Import as member   Michael Ilseman
• [swift-evolution] [Proposal draft] Import as member   Jeff Kelley
• [swift-evolution] [Proposal] Allow static protocol extension methods to be called directly on the protocol   Rasmus Kjeldsen
• [swift-evolution] [Proposal] Allow static protocol extension methods to be called directly on the protocol   Joe Groff
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Haravikk
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dave Abrahams
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Brent Royal-Gordon
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dave Abrahams
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dave Abrahams
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Brent Royal-Gordon
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Brent Royal-Gordon
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dave Abrahams
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dave Abrahams
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Brent Royal-Gordon
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Patrick Pijnappel
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dmitri Gribenko
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Patrick Pijnappel
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Patrick Pijnappel
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dmitri Gribenko
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Patrick Pijnappel
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Dmitri Gribenko
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Patrick Pijnappel
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change guarantee for GeneratorType.next() to always return nil past end   Kevin Ballard
• [swift-evolution] [Proposal] Change infix operator attributes syntax to be more consistent with the rest of the language   Brent Royal-Gordon
• [swift-evolution] [Proposal] Change infix operator attributes syntax to be more consistent with the rest of the language   Jean-Daniel Dupas
• [swift-evolution] [Proposal] Change infix operator attributes syntax to be more consistent with the rest of the language   Антон Жилин
• [swift-evolution] [Proposal] Change infix operator attributes syntax to be more consistent with the rest of the language   Антон Жилин
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Xiaodi Wu
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Haravikk
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Seth Friedman
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Dmitri Gribenko
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Ross O'Brien
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Xiaodi Wu
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Xiaodi Wu
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Seth Friedman
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Brent Royal-Gordon
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Dmitri Gribenko
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Brent Royal-Gordon
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Xiaodi Wu
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Thorsten Seitz
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Dave Abrahams
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Dave Abrahams
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Erica Sadun
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Xiaodi Wu
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Howard Lovatt
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Dave Abrahams
• [swift-evolution] [Proposal] Conventionalizing stride semantics   Thorsten Seitz
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Charles Kissinger
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Brent Royal-Gordon
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Erica Sadun
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Jonathan Tang
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Howard Lovatt
• [swift-evolution] [Proposal] Decoupling Floating Point Strides from Generic Implementations   Dany St-Amant
• [swift-evolution] [Proposal] Instance Operators   Thorsten Seitz
• [swift-evolution] [Proposal] Instance Operators   Andrew Bennett
• [swift-evolution] [Proposal] Instance Operators   Haravikk
• [swift-evolution] [Proposal] Instance Operators   davesweeris at mac.com
• [swift-evolution] [Proposal] Instance Operators   Haravikk
• [swift-evolution] [Proposal] Mixins   Антон Жилин
• [swift-evolution] [proposal]Decouple definition of Int8 from target char type   William Dillon
• [swift-evolution] [proposal]Decouple definition of Int8 from target char type   Dmitri Gribenko
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Dmitri Gribenko
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Patrick Pijnappel
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Jeremy Pereira
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Adrian Kashivskyy
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Adrian Kashivskyy
• [swift-evolution] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Joe Groff
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Matthew Judge
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Alsey Miller
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Austin Zheng
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Scrève
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Alsey Miller
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Scrève
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Alsey Miller
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Scrève
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Austin Zheng
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Evan Maloney
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Dietmar Planitzer
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Scrève
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Hart
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   David Hart
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Adrian Kashivskyy
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Haravikk
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Matthew Judge
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Gwendal Roué
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Gwendal Roué
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Wallacy
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Gwendal Roué
• [swift-evolution] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Haravikk
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Stephen Celis
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   David Hart
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Alex Hoppen
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Chris Lattner
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Trent Nadeau
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   William Dillon
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Patrick Pijnappel
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Jacob Bandes-Storch
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Thorsten Seitz
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Howard Lovatt
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Pelaia II, Tom
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Rudolf Adamkovic
• [swift-evolution] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Adrian Kashivskyy
• [swift-evolution] [RFC] New collections model: collections advance indices   Károly Lőrentey
• [swift-evolution] [RFC] New collections model: collections advance indices   Brent Royal-Gordon
• [swift-evolution] [RFC] New collections model: collections advance indices   Dave Abrahams
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   Dave Abrahams
• [swift-evolution] [RFC] New collections model: collections advance indices   Károly Lőrentey
• [swift-evolution] [RFC] New collections model: collections advance indices   Dave Abrahams
• [swift-evolution] [RFC] New collections model: collections advance indices   Dave Abrahams
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   Trent Nadeau
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   Trent Nadeau
• [swift-evolution] [RFC] New collections model: collections advance indices   Howard Lovatt
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   plx
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [RFC] New collections model: collections advance indices   Dmitri Gribenko
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   Brent Royal-Gordon
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   Dietmar Planitzer
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   John McCall
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   Joe Groff
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   Douglas Gregor
• [swift-evolution] [swift-dev] Is there an underlying reason why optional protocol requirements need @objc?   Joe Groff
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   David Owens II
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   David Owens II
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Nicola Salmoria
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Jim Kubicek
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Jonathan Tang
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [swift-evolution-announce] [Review] SE-0025 Scoped Access Level   Ilya Belenkiy
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   David Owens II
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Goffredo Marocchi
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Gwendal Roué
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Gwendal Roué
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Goffredo Marocchi
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [swift-evolution-announce] [Review] SE-0026 Abstract classes and methods   Thorsten Seitz
• [swift-evolution] [swift-evolution-announce] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Brent Royal-Gordon
• [swift-evolution] [swift-evolution-announce] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Patrick Gili
• [swift-evolution] [swift-evolution-announce] [Review] SE-0040 Replacing Equal Signs with Colons For Attribute Arguments   Paul Ossenbruggen
• [swift-evolution] [swift-users] Every non-trivial Swift function should throw, right?   Erica Sadun
• [swift-evolution] Antwort: Re: Exceptions with guard-clause as shorthand instead of do/try/catch   Matis Schotte
• [swift-evolution] Antwort: Re: Exceptions with guard-clause as shorthand instead of do/try/catch   Jacob Bandes-Storch
• [swift-evolution] Better Swift interface for NSDecimal   Tony Parker
• [swift-evolution] Changes to RangeReplaceableCollectionType   Dmitri Gribenko
• [swift-evolution] Changes to RangeReplaceableCollectionType   Haravikk
• [swift-evolution] Changes to RangeReplaceableCollectionType   Dmitri Gribenko
• [swift-evolution] Changes to RangeReplaceableCollectionType   Haravikk
• [swift-evolution] Changes to RangeReplaceableCollectionType   Dmitri Gribenko
• [swift-evolution] Changes to RangeReplaceableCollectionType   Haravikk
• [swift-evolution] Changes to RangeReplaceableCollectionType   Dmitri Gribenko
• [swift-evolution] Exceptions with guard-clause as shorthand instead of do/try/catch   Stephen Celis
• [swift-evolution] Exceptions with guard-clause as shorthand instead of do/try/catch   Matis Schotte
• [swift-evolution] Idea: Extend "guard" to try-statements, with a catch block   Jacob Bandes-Storch
• [swift-evolution] Idea: Extend "guard" to try-statements, with a catch block   Stephen Celis
• [swift-evolution] Idea: Extend "guard" to try-statements, with a catch block   Chris Lattner
• [swift-evolution] Idea: Extend "guard" to try-statements, with a catch block   Jacob Bandes-Storch
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Pyry Jahkola
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   David Sweeris
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   davesweeris at mac.com
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   ted van gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   ted van gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   ted van gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   ted van gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Pyry Jahkola
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Tino Heth
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Ted F.A. van Gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Félix Cloutier
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Ted F.A. van Gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Ted F.A. van Gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Ted F.A. van Gaalen
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Joe Groff
• [swift-evolution] implementing real (floating point) number comparison tolerance as a compiler directive.   Stephen Canon
• [swift-evolution] Is there an underlying reason why optional protocol requirements need @objc? (from -dev)   Dave Abrahams
• [swift-evolution] Mailman?   Jacob Bandes-Storch
• [swift-evolution] Make non-void functions @warn_unused_result by default   Pyry Jahkola
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Stephen Celis
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Tino Heth
• [swift-evolution] Make non-void functions @warn_unused_result by default   Tino Heth
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Brent Royal-Gordon
• [swift-evolution] Make non-void functions @warn_unused_result by default   Brent Royal-Gordon
• [swift-evolution] Make non-void functions @warn_unused_result by default   Stephen Celis
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Chris Lattner
• [swift-evolution] Make non-void functions @warn_unused_result by default   Paul Ossenbruggen
• [swift-evolution] Make non-void functions @warn_unused_result by default   Step C
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Hart
• [swift-evolution] Make non-void functions @warn_unused_result by default   Austin Zheng
• [swift-evolution] Make non-void functions @warn_unused_result by default   Tino Heth
• [swift-evolution] Make non-void functions @warn_unused_result by default   Tino Heth
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   Brent Royal-Gordon
• [swift-evolution] Make non-void functions @warn_unused_result by default   Andrew Bennett
• [swift-evolution] Make non-void functions @warn_unused_result by default   Tino Heth
• [swift-evolution] Make non-void functions @warn_unused_result by default   Davide De Franceschi
• [swift-evolution] Make non-void functions @warn_unused_result by default   Step C
• [swift-evolution] Make non-void functions @warn_unused_result by default   Step C
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [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] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   Gwendal Roué
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Jeff Kelley
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Dmitri Gribenko
• [swift-evolution] Make non-void functions @warn_unused_result by default   Erica Sadun
• [swift-evolution] Make non-void functions @warn_unused_result by default   Haravikk
• [swift-evolution] Make non-void functions @warn_unused_result by default   David Owens II
• [swift-evolution] Make non-void functions @warn_unused_result by default   Andrey Tarantsov
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   David Hart
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   Erica Sadun
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   Chris Lattner
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   Chris Lattner
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   Joe Groff
• [swift-evolution] Pitch: make class initialization complexity more progressively disclosed   Thorsten Seitz
• [swift-evolution] Proposal: Add scan, takeWhile, dropWhile, and iterate to the stdlib   Dave Abrahams
• [swift-evolution] Proposal: Add scan, takeWhile, dropWhile, and iterate to the stdlib   Erica Sadun
• [swift-evolution] Proposal: Add scan, takeWhile, dropWhile, and iterate to the stdlib   Thorsten Seitz
• [swift-evolution] Proposal: An assignment operator := that ensures nil before assignment.   Andrey Tarantsov
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Developer
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Paul Ossenbruggen
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Brent Royal-Gordon
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Erica Sadun
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Erica Sadun
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Dave Abrahams
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Kevin Lundberg
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Radosław Pietruszewski
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Radosław Pietruszewski
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Kevin Lundberg
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   T.J. Usiyan
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Kevin Lundberg
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Kevin Lundberg
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Kevin Lundberg
• [swift-evolution] Proposal: change infix operator attributes syntax to be more consistent with the rest of the language   Dave Abrahams
• [swift-evolution] Proposal: conversion protocol naming conventions   Brad Hilton
• [swift-evolution] Proposal: conversion protocol naming conventions   Dave Abrahams
• [swift-evolution] Proposal: conversion protocol naming conventions   Erica Sadun
• [swift-evolution] Proposal: conversion protocol naming conventions   brad.hilton.nw at gmail.com
• [swift-evolution] Proposal: conversion protocol naming conventions   Howard Lovatt
• [swift-evolution] Proposal: pattern match based on associated value(s) only   Andrey Tarantsov
• [swift-evolution] Proposal: Swift should automatically modify your code to improve compile times.   Chris Lattner
• [swift-evolution] Proposal: Swift should automatically modify your code to improve compile times.   Amir Michail
• [swift-evolution] Proposal: Swift should automatically modify your code to improve compile times.   James Campbell
• [swift-evolution] Proposal: Swift should automatically modify your code to improve compile times.   Amir Michail
• [swift-evolution] Proposal: Swift should automatically modify your code to improve compile times.   Amir Michail
• [swift-evolution] Pull requests on Swift Evolution   Erica Sadun
• [swift-evolution] Remove Failable Initializers   James Campbell
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Howard Lovatt
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Chris Lattner
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Ross O'Brien
• [swift-evolution] Remove Failable Initializers   James Campbell
• [swift-evolution] Remove Failable Initializers   Kyle Sherman
• [swift-evolution] Remove Failable Initializers   Austin Zheng
• [swift-evolution] Remove Failable Initializers   David Hart
• [swift-evolution] Remove Failable Initializers   Patrick Pijnappel
• [swift-evolution] Remove Failable Initializers   James Campbell
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   James Campbell
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   Radosław Pietruszewski
• [swift-evolution] Remove Failable Initializers   Kyle Sherman
• [swift-evolution] Remove Failable Initializers   Patrick Gili
• [swift-evolution] Remove Failable Initializers   Charles Kissinger
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Félix Cloutier
• [swift-evolution] Remove Failable Initializers   Chris Lattner
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Félix Cloutier
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Andrew Bennett
• [swift-evolution] Remove Failable Initializers   James Campbell
• [swift-evolution] Remove Failable Initializers   Félix Cloutier
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Félix Cloutier
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   Thorsten Seitz
• [swift-evolution] Remove Failable Initializers   Thorsten Seitz
• [swift-evolution] Remove Failable Initializers   Thorsten Seitz
• [swift-evolution] Remove Failable Initializers   Haravikk
• [swift-evolution] Remove Failable Initializers   Brent Royal-Gordon
• [swift-evolution] Remove Failable Initializers   Jean-Daniel Dupas
• [swift-evolution] Remove Failable Initializers   Антон Жилин
• [swift-evolution] Remove Failable Initializers   Myles Schultz
• [swift-evolution] Strider with 'from', 'to', 'by 'and 'tolerance' parameters .   Ted F.A. van Gaalen
• [swift-evolution] Striding Through Lands of Iteration   Ted F.A. van Gaalen
• [swift-evolution] There should be no reserved words (keywords) ?   Ted F.A. van Gaalen
• [swift-evolution] There should be no reserved words (keywords) ?   Adrian Kashivskyy
• [swift-evolution] There should be no reserved words (keywords) ?   Ted F.A. van Gaalen
• [swift-evolution] There should be no reserved words (keywords) ?   Joe Groff

Last message date: Sun Mar 6 23:19:20 CST 2016
Archived on: Mon Mar 7 10:24:43 CST 2016

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