The Week Of Monday 2 May 2016 Archives by thread

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

Starting: Mon May 2 02:16:09 CDT 2016
Ending: Sun May 8 23:24:06 CDT 2016
Messages: 590

• [swift-evolution] Move where clause to end of declaration   David Hart
  • [swift-evolution] Move where clause to end of declaration   Developer
    • [swift-evolution] Move where clause to end of declaration   David Hart
      • [swift-evolution] Move where clause to end of declaration   David Hart
  • [swift-evolution] Move where clause to end of declaration   Pyry Jahkola
    • [swift-evolution] Move where clause to end of declaration   David Hart
  • [swift-evolution] Move where clause to end of declaration   Dany St-Amant
    • [swift-evolution] Move where clause to end of declaration   David Hart
• [swift-evolution] [Idea] Remove optional pattern binding   Haravikk
  • [swift-evolution] [Idea] Remove optional pattern binding   Антон Жилин
    • [swift-evolution] [Idea] Remove optional pattern binding   Haravikk
• [swift-evolution] multi-line string literals.   Haravikk
  • [swift-evolution] multi-line string literals.   Basem Emara
  • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
    • [swift-evolution] multi-line string literals.   Rainer Brockerhoff
      • [swift-evolution] multi-line string literals.   Chris Blessing
• [swift-evolution] multi-line string literals.   John Holdsworth
  • [swift-evolution] multi-line string literals.   LM
  • [swift-evolution] multi-line string literals.   L. Mihalkovic
    • [swift-evolution] multi-line string literals.   John Holdsworth
      • [swift-evolution] multi-line string literals.   L. Mihalkovic
      • [swift-evolution] multi-line string literals.   John Holdsworth
      • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
      • [swift-evolution] multi-line string literals.   Tyler Fleming Cloutier
      • [swift-evolution] multi-line string literals.   L. Mihalkovic
      • [swift-evolution] multi-line string literals.   Michael Peternell
      • [swift-evolution] multi-line string literals.   David Hart
      • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   John Holdsworth
      • [swift-evolution] multi-line string literals.   Tyler Cloutier
      • [swift-evolution] multi-line string literals.   Tyler Cloutier
      • [swift-evolution] multi-line string literals.   Matthew Johnson
      • [swift-evolution] multi-line string literals.   L. Mihalkovic
      • [swift-evolution] multi-line string literals.   Matthew Johnson
      • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
      • [swift-evolution] multi-line string literals.   Matthew Johnson
      • [swift-evolution] multi-line string literals.   L Mihalkovic
      • [swift-evolution] multi-line string literals.   L Mihalkovic
      • [swift-evolution] multi-line string literals.   Tyler Cloutier
      • [swift-evolution] multi-line string literals.   John Holdsworth
      • [swift-evolution] [Pitch] multiline string literals   L Mihalkovic
      • [swift-evolution] multi-line string literals.   Cole Campbell
      • [swift-evolution] multi-line string literals.   L Mihalkovic
      • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
      • [swift-evolution] multi-line string literals.   Sean Heber
      • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   Michael Peternell
• [swift-evolution] throw expressions in ternary operators   David Hart
  • [swift-evolution] throw expressions in ternary operators   Krzysztof Siejkowski
    • [swift-evolution] throw expressions in ternary operators   David Hart
      • [swift-evolution] throw expressions in ternary operators   Krzysztof Siejkowski
      • [swift-evolution] throw expressions in ternary operators   Chris Lattner
• [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   John McCall
    • [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Adrian Zubarev
    • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Adrian Zubarev
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
    • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Jesse Squires
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Basem Emara
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tino Heth
• [swift-evolution] [Review] SE-0072: Fully eliminate implicit bridging conversions from Swift   Jordan Rose
  • [swift-evolution] [Review] SE-0072: Fully eliminate implicit bridging conversions from Swift   Joe Pamer
    • [swift-evolution] [Review] SE-0072: Fully eliminate implicit bridging conversions from Swift   Jordan Rose
• [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Joe Groff
• [swift-evolution] [Idea] Remove optional pattern binding   Jordan Rose
  • [swift-evolution] [Idea] Remove optional pattern binding   John McCall
    • [swift-evolution] [Idea] Remove optional pattern binding   Chris Lattner
      • [swift-evolution] [Idea] Remove optional pattern binding   John McCall
      • [swift-evolution] [Idea] Remove optional pattern binding   Антон Жилин
      • [swift-evolution] [Idea] Remove optional pattern binding   John McCall
      • [swift-evolution] [Idea] Remove optional pattern binding   Chris Lattner
      • [swift-evolution] [Idea] Remove optional pattern binding   John McCall
      • [swift-evolution] [Idea] Remove optional pattern binding   David Hart
      • [swift-evolution] [Idea] Remove optional pattern binding   John McCall
      • [swift-evolution] [Idea] Remove optional pattern binding   Krzysztof Siejkowski
      • [swift-evolution] [Idea] Remove optional pattern binding   Michael Peternell
      • [swift-evolution] [Idea] Remove optional pattern binding   David Waite
      • [swift-evolution] [Idea] Remove optional pattern binding   Tyler Cloutier
• [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Xiaodi Wu
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Xiaodi Wu
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Chris Lattner
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   David Sweeris
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Xiaodi Wu
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Chris Lattner
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   David Sweeris
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
      • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dave Abrahams
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Shawn Erickson
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Chris Lattner
  • [swift-evolution] [Proposal] Improving operator requirements in protocols   Dmitri Gribenko
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Pyry Jahkola
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Nicola Salmoria
    • [swift-evolution] [Proposal] Improving operator requirements in protocols   Tony Allevato
• [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Dave Abrahams
  • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Xiaodi Wu
    • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Dave Abrahams
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Xiaodi Wu
  • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Joe Groff
    • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Dave Abrahams
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Jose Cheyo Jimenez
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Joe Groff
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Dave Abrahams
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Chris Lattner
      • [swift-evolution] Trial balloon: conforming sizeof, sizeofValue, etc. to naming guidelines   Xiaodi Wu
• [swift-evolution] [Review] SE-0052: Change IteratorType post-nil guarantee   Michael Peternell
• [swift-evolution] proposal for a even simpler guard.. => guard!   Dominik Pich
  • [swift-evolution] proposal for a even simpler guard.. => guard!   David Waite
    • [swift-evolution] proposal for a even simpler guard.. => guard!   Dominik Pich
  • [swift-evolution] proposal for a even simpler guard.. => guard!   Jordan Rose
    • [swift-evolution] proposal for a even simpler guard.. => guard!   Dominik Pich
      • [swift-evolution] proposal for a even simpler guard.. => guard!   Xiaodi Wu
      • [swift-evolution] proposal for a even simpler guard.. => guard!   Rod Brown
      • [swift-evolution] proposal for a even simpler guard.. => guard!   Austin Zheng
      • [swift-evolution] proposal for a even simpler guard.. => guard!   Dave Abrahams
• [swift-evolution] Auto Unwrapping Of Optionals   Tod Cunningham
  • [swift-evolution] Auto Unwrapping Of Optionals   David Waite
    • [swift-evolution] Auto Unwrapping Of Optionals   Rod Brown
      • [swift-evolution] Auto Unwrapping Of Optionals   Tod Cunningham
      • [swift-evolution] Auto Unwrapping Of Optionals   Josh Parmenter
  • [swift-evolution] Auto Unwrapping Of Optionals   Rod Brown
• [swift-evolution] Protocol non-conformance clause   Thorsten Seitz
• [swift-evolution] [Pitch] Permit self in type-inferred property initializers   Marc Prud'hommeaux
• [swift-evolution] [Idea] Make lazy an attribute   Антон Жилин
  • [swift-evolution] [Idea] Make lazy an attribute   David Sweeris
    • [swift-evolution] [Idea] Make lazy an attribute   Антон Жилин
• [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Chris Lattner
  • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Erica Sadun
    • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Chris Lattner
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Erica Sadun
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   David Hart
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Chris Lattner
    • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Charles Srstka
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   T.J. Usiyan
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Joe Groff
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Charles Srstka
  • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Joe Groff
    • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Chris Lattner
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Joe Groff
      • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Charles Srstka
• [swift-evolution] [Review] SE-0065 A New Model for Collections and Indices   Karl
  • [swift-evolution] [Review] SE-0065 A New Model for Collections and Indices   Dmitri Gribenko
• [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   David Hart
• [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   David Hart
• [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   David Hart
  • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Douglas Gregor
    • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Matthew Johnson
      • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Thorsten Seitz
      • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Matthew Johnson
      • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   David Hart
      • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Matthew Johnson
  • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Dave Abrahams
    • [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   David Hart
• [swift-evolution] [Manifesto] Completing Generics   David Hart
  • [swift-evolution] [Manifesto] Completing Generics   Douglas Gregor
    • [swift-evolution] [Manifesto] Completing Generics   David Hart
      • [swift-evolution] [Manifesto] Completing Generics   David Hart
      • [swift-evolution] [Manifesto] Completing Generics   Austin Zheng
      • [swift-evolution] [Manifesto] Completing Generics   David Hart
      • [swift-evolution] [Manifesto] Completing Generics   Austin Zheng
• [swift-evolution] Auto Unwrapping Of Optionals   Tyler Cloutier
• [swift-evolution] [Review] SE-0052: Change IteratorType post-nil guarantee   Max Moiseev
• [swift-evolution] [Accepted] SE-0067: Enhanced Floating Point Protocols   Chris Lattner
  • [swift-evolution] [Accepted] SE-0067: Enhanced Floating Point Protocols   Xiaodi Wu
    • [swift-evolution] [Accepted] SE-0067: Enhanced Floating Point Protocols   Xiaodi Wu
• [swift-evolution] [Accepted] SE-0071: Allow (most) keywords in member references   Chris Lattner
• [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Sangjin Han
  • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   hitstergtd+swiftevo at gmail.com
    • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Michael Buckley
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   David Owens II
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Michael Buckley
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   John McCall
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Chris Lattner
    • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Joe Groff
  • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Jordan Rose
    • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Joe Groff
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   John McCall
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Joe Groff
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   James Berry
    • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Chris Lattner
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Joe Groff
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Chris Lattner
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Joe Groff
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Chris Lattner
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   hitstergtd+swiftevo at gmail.com
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Sangjin Han
    • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Michael Peternell
      • [swift-evolution] #if os(Windows) and MSVC/Cygwin Compatibility   Jordan Rose
• [swift-evolution] [Review] SE-0052: Change IteratorType post-nil guarantee   Kevin Ballard
  • [swift-evolution] [Review] SE-0052: Change IteratorType post-nil guarantee   Patrick Pijnappel
• [swift-evolution] [swift-evolution-announce] [Review] SE-0017: Change Unmanaged to use UnsafePointer   Kevin Ballard
• [swift-evolution] Feature proposal: Range operator with step   Hans Huck
• [swift-evolution] Auto Unwrapping Of Optionals   Cristián Arenas Ulloa
• [swift-evolution] [Pitch] Reference storage for enum associated values   Marc Prud'hommeaux
  • [swift-evolution] [Pitch] Reference storage for enum associated values   Haravikk
  • [swift-evolution] [Pitch] Reference storage for enum associated values   Patrick Smith
  • [swift-evolution] [Pitch] Reference storage for enum associated values   Michael Peternell
    • [swift-evolution] [Pitch] Reference storage for enum associated values   Marc Prud'hommeaux
      • [swift-evolution] [Pitch] Reference storage for enum associated values   Michael Peternell
      • [swift-evolution] [Pitch] Reference storage for enum associated values   Marc Prud'hommeaux
  • [swift-evolution] [Pitch] Reference storage for enum associated values   Joe Groff
    • [swift-evolution] [Pitch] Reference storage for enum associated values   Marc Prud'hommeaux
• [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   J.D. Healy
• [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Joe Groff
• [swift-evolution] [Accepted] SE-0061: Add Generic Result and Error Handling to autoreleasepool()   Chris Lattner
• [swift-evolution] [Accepted] SE-0070: Make Optional Requirements Objective-C-only   Chris Lattner
• [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Charles Srstka
• [swift-evolution] multi-line string literals.   Dave Abrahams
• [swift-evolution] multi-line string literals.   Dave Abrahams
• [swift-evolution] [Oversight] Reference types allow mutating methods through generics   James Froggatt
  • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Jordan Rose
    • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   James Froggatt
    • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   T.J. Usiyan
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   James Froggatt
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Joe Groff
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   David Sweeris
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   David Sweeris
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   David Sweeris
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   David Sweeris
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Joe Groff
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Matthew Johnson
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Joe Groff
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
      • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Dave Abrahams
    • [swift-evolution] [Oversight] Reference types allow mutating methods through generics   Joe Groff
• [swift-evolution] [Pitch] Reference storage for enum associated values   James Froggatt
• [swift-evolution] Should we rename "class" when referring to protocol conformance?   James Froggatt
• [swift-evolution] Should we rename "class" when referring to protocol conformance?   James Froggatt
• [swift-evolution] [Proposal/Pitch] Function decorators   Aleksandar Petrovic
  • [swift-evolution] [Proposal/Pitch] Function decorators   Karl Wagner
• [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Joe Groff
  • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Adrian Zubarev
  • [swift-evolution] [Pitch] Reducing the bridging magic in dynamic casts   Jose Cheyo Jimenez
• [swift-evolution] Introduce OrderedSet type   Nicholas Maccharoli
  • [swift-evolution] Introduce OrderedSet type   Rod Brown
    • [swift-evolution] [Review] SE-0069: Mutability and Foundation Value Types   Rod Brown
      • [swift-evolution] [Review] SE-0069: Mutability and Foundation Value Types   Tony Parker
    • [swift-evolution] Introduce OrderedSet type   Austin Zheng
• [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Chris Lattner
  • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Charles Srstka
  • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Matthew Johnson
  • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Michael Peternell
  • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Erica Sadun
    • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Matthew Johnson
    • [swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters   Dave Abrahams
• [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Chris Lattner
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Pyry Jahkola
    • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Gwendal Roué
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Pyry Jahkola
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Gwendal Roué
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Dmitri Gribenko
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Gwendal Roué
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Dmitri Gribenko
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Gwendal Roué
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   David Hart
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Nicola Salmoria
    • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Gwendal Roué
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Matthew Johnson
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Dave Abrahams
    • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   T.J. Usiyan
    • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Andrew Bennett
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Dave Abrahams
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Andrew Bennett
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Matthew Johnson
      • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Andrew Bennett
  • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Greg Parker
    • [swift-evolution] [Review] SE-0073: Marking closures as executing exactly once   Rod Brown
• [swift-evolution] [Review] SE-0074: Implementation of Binary Search functions   Chris Lattner
  • [swift-evolution] [Review] SE-0074: Implementation of Binary Search functions   Xiaodi Wu
  • [swift-evolution] [Review] SE-0074: Implementation of Binary Search functions   T.J. Usiyan
  • [swift-evolution] [Review] SE-0074: Implementation of Binary Search functions   Nicola Salmoria
  • [swift-evolution] [Review] SE-0074: Implementation of Binary Search functions   Dave Abrahams
• [swift-evolution] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Chris Lattner
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Andrew Trick
    • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Joe Groff
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Jordan Rose
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Andrew Trick
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Jordan Rose
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Joe Groff
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Andrew Trick
  • [swift-evolution] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Guillaume Lessard
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0076: Add overrides taking an UnsafePointer source to non-destructive copying methods on UnsafeMutablePointer   Max Moiseev
• [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Chris Lattner
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Matthew Johnson
  • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dmitri Gribenko
    • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Nate Cook
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dmitri Gribenko
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Nate Cook
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dmitri Gribenko
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dave Abrahams
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Nate Cook
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dave Abrahams
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Nate Cook
      • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Dave Abrahams
• [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Chris Lattner
  • [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Charles Srstka
    • [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Chris Lattner
    • [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
  • [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Gwendal Roué
    • [swift-evolution] [Review] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Stephen Canon
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Colin Barrett
    • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Colin Barrett
    • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Dave Abrahams
  • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Max Moiseev
    • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Max Moiseev
      • [swift-evolution] [swift-evolution-announce] [Review] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
• [swift-evolution] [Proposal] Tuple Extensions   Developer
  • [swift-evolution] [Proposal] Tuple Extensions   Robert Widmann
  • [swift-evolution] [Proposal] Tuple Extensions   Joe Groff
    • [swift-evolution] [Proposal] Tuple Extensions   Austin Zheng
      • [swift-evolution] [Proposal] Tuple Extensions   Chris Lattner
    • [swift-evolution] [Proposal] Tuple Extensions   Robert Widmann
      • [swift-evolution] [Proposal] Tuple Extensions   Joe Groff
      • [swift-evolution] [Proposal] Tuple Extensions   Robert Widmann
      • [swift-evolution] [Proposal] Tuple Extensions   Joe Groff
• [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Xiaodi Wu
  • [swift-evolution] [Review] SE-0078: Implement a rotate algorithm, equivalent to std::rotate() in C++   Nate Cook
• [swift-evolution] Should we rename "class" when referring to protocol conformance?   James Froggatt
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Adrian Zubarev
    • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Adrian Zubarev
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Andrew Trick
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Andrew Trick
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Andrew Trick
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   L Mihalkovic
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Matthew Johnson
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Adrian Zubarev
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Tyler Fleming Cloutier
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Dave Abrahams
      • [swift-evolution] Should we rename "class" when referring to protocol conformance?   David Sweeris
  • [swift-evolution] Should we rename "class" when referring to protocol conformance?   Patrick Smith
• [swift-evolution] Property observers in protocol extensions   Andru Felipe Zuniga
• [swift-evolution] [Pitch] Richer function identifiers, simpler function types   Alex Hoppen
• [swift-evolution] [Review] SE-0082: Package Manager Editable Packages   Anders Bertelrud
• [swift-evolution] [Review] SE-0072: Fully eliminate implicit bridging conversions from Swift   Joe Pamer
• [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Erica Sadun
  • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Jacob Bandes-Storch
  • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Robert Widmann
    • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Michael Peternell
  • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Jordan Rose
    • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Josh Parmenter
    • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   David Owens II
    • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Chris Lattner
      • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   David Hart
  • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Haravikk
  • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Tino Heth
    • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Goffredo Marocchi
      • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Jacopo Andrea Giola
      • [swift-evolution] [Pitch] Including yes/no in stdlib as aliases for true/false   Adrian Zubarev
• [swift-evolution] [Pitch] merge types and protocols back together with type<Type, Protocol, ...>   Adrian Zubarev
• [swift-evolution] [Proposal] Tuple Extensions   Robert Widmann
• [swift-evolution] [Proposal] Tuple Extensions   Robert Widmann
• [swift-evolution] [Pitch] Reference equivalent to value-type 'enum'   Austin Zheng
  • [swift-evolution] [Pitch] Reference equivalent to value-type 'enum'   Matthew Johnson
    • [swift-evolution] [Pitch] Reference equivalent to value-type 'enum'   Joshua Kopin
• [swift-evolution] [Accepted] SE-0069: Mutability and Foundation Value Types   Chris Lattner
• [swift-evolution] [Accepted] SE-0017: Change Unmanaged to use UnsafePointer   Chris Lattner
• [swift-evolution] [Accepted] SE-0032: Add find method to Sequence   Chris Lattner
• [swift-evolution] [Accepted] SE-0052: Change IteratorType post-nil guarantee   Chris Lattner
• [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Chris Lattner
  • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Erica Sadun
    • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Chris Lattner
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Erica Sadun
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Matthew Johnson
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Brent Royal-Gordon
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Patrick Smith
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   David Hart
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Cole Campbell
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Gmail
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Matthew Johnson
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Matthew Johnson
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Matthew Johnson
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   David Hart
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Chris Lattner
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
    • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Erica Sadun
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Chris Lattner
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
  • [swift-evolution] [swift-evolution-announce] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Pierre Grabolosa
  • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
    • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Dave Abrahams
      • [swift-evolution] [Accepted with modifications] SE-0045: Add scan, prefix(while:), drop(while:), and unfold to the stdlib   Kevin Ballard
• [swift-evolution] SE-0080: Failable Numeric Conversion Initializers   William Shipley
  • [swift-evolution] SE-0080: Failable Numeric Conversion Initializers   Matthew Johnson
• [swift-evolution] [Pitch] Reference equivalent to value-type 'enum'   James Froggatt
  • [swift-evolution] [Pitch] Reference equivalent to value-type 'enum'   Austin Zheng
• [swift-evolution] [Pitch] make == more restrictive at compile time   Gerd Castan
  • [swift-evolution] [Pitch] make == more restrictive at compile time   Robert Widmann
  • [swift-evolution] [Pitch] make == more restrictive at compile time   Joe Groff
• [swift-evolution] Referencing zero-parameter functions   Alex Hoppen
  • [swift-evolution] Referencing zero-parameter functions   David Sweeris
    • [swift-evolution] Referencing zero-parameter functions   Alex Hoppen
      • [swift-evolution] Referencing zero-parameter functions   Xiaodi Wu
      • [swift-evolution] Referencing zero-parameter functions   Jordan Rose
      • [swift-evolution] Referencing zero-parameter functions   Chris Lattner
      • [swift-evolution] Referencing zero-parameter functions   Kurt Werle
      • [swift-evolution] Referencing zero-parameter functions   Jordan Rose
      • [swift-evolution] Referencing zero-parameter functions   Joe Groff
      • [swift-evolution] Referencing zero-parameter functions   Alex Hoppen
      • [swift-evolution] Referencing zero-parameter functions   Xiaodi Wu
      • [swift-evolution] Referencing zero-parameter functions   Alex Hoppen
      • [swift-evolution] Referencing zero-parameter functions   Chris Lattner
• [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Jordan Rose
  • [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   David Sweeris
  • [swift-evolution] Case conventions for mixed-case words (like   Justin Jia
    • [swift-evolution] Case conventions for mixed-case words (like   Haravikk
      • [swift-evolution] Case conventions for mixed-case words (like   Xiaodi Wu
      • [swift-evolution] Case conventions for mixed-case words (like   Jordan Rose
• [swift-evolution] Switch on an optional enum -- `case: nil`?   Eric Miller
  • [swift-evolution] Switch on an optional enum -- `case: nil`?   Krzysztof Siejkowski
    • [swift-evolution] Switch on an optional enum -- `case: nil`?   Ross O'Brien
    • [swift-evolution] Switch on an optional enum -- `case: nil`?   David Sweeris
      • [swift-evolution] Switch on an optional enum -- `case: nil`?   Eric Miller
  • [swift-evolution] Switch on an optional enum -- `case: nil`?   David Sweeris
• [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Jordan Rose
  • [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Basem Emara
    • [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Jordan Rose
      • [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Patrick Smith
  • [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Matthew Johnson
• [swift-evolution] Case conventions for mixed-case words (like "iPad" and "NaN")   Антон Жилин
• [swift-evolution] multi-line string literals.   Doug McKenna
• [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Dennis Weissmann
  • [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   T.J. Usiyan
  • [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Gmail
  • [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Geordie J
• [swift-evolution] [Pitch] Consistent bridging for NSErrors at the language boundary   Charles Srstka
  • [swift-evolution] [Pitch] Consistent bridging for NSErrors at the language boundary   Charles Srstka
• [swift-evolution] Making `.self` After `Type` Optional   Joe Groff
  • [swift-evolution] Making `.self` After `Type` Optional   David Hart
    • [swift-evolution] Making `.self` After `Type` Optional   Austin Zheng
    • [swift-evolution] Making `.self` After `Type` Optional   Pyry Jahkola
      • [swift-evolution] Making `.self` After `Type` Optional   Adrian Zubarev
      • [swift-evolution] Making `.self` After `Type` Optional   Pyry Jahkola
      • [swift-evolution] Making `.self` After `Type` Optional   Adrian Zubarev
    • [swift-evolution] Making `.self` After `Type` Optional   Joe Groff
  • [swift-evolution] Making `.self` After `Type` Optional   Matthew Johnson
• [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Chris Lattner
  • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Jacob Bandes-Storch
    • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Joe Groff
      • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Charles Srstka
      • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Jacob Bandes-Storch
      • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Charles Srstka
      • [swift-evolution] [Accepted] SE-0072: Fully eliminate implicit bridging conversions from Swift   Zach Waldowski
• [swift-evolution] [Review] SE-0066: Standardize function type argument syntax to require parentheses   T.J. Usiyan
• [swift-evolution] [Accepted] SE-0066: Standardize function type argument syntax to require parentheses   Douglas Gregor
• [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Thorsten Seitz
  • [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Goffredo Marocchi
    • [swift-evolution] [Pitch] Tuple Destructuring in Parameter Lists   Cole Campbell
• [swift-evolution] [Pitch] Allow nested protocol declarations   Adrian Zubarev
• [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String   Morten Bek Ditlevsen
  • [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String   Dmitri Gribenko
  • [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String   Joe Groff
    • [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String   Stephen Canon
      • [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String   Joe Groff
• [swift-evolution] Idea: Allow/require "let" in property setter name declarations   Ian Partridge
  • [swift-evolution] Idea: Allow/require "let" in property setter name declarations   Haravikk
    • [swift-evolution] Idea: Allow/require "let" in property setter name declarations   Geordie J
  • [swift-evolution] Idea: Allow/require "let" in property setter name declarations   Chris Lattner
• [swift-evolution] [Proposal] More Powerful Constraints for Associated Types   Thorsten Seitz
• [swift-evolution] [Pitch] New enum syntax.   James Froggatt
• [swift-evolution] [Proposal] More lenient subscript methods over Collections (was: [Proposal] Safer half-open range operator)   Luis Henrique B. Sousa
  • [swift-evolution] [Proposal] More lenient subscript methods over Collections (was: [Proposal] Safer half-open range operator)   Matthew Johnson
    • [swift-evolution] [Proposal] More lenient subscript methods over Collections (was: [Proposal] Safer half-open range operator)   Luis Henrique B. Sousa
• [swift-evolution] [Proposal] Multiline string literals   Michael Peternell
• [swift-evolution] Dropping NS Prefix in Foundation   Tony Parker
  • [swift-evolution] Dropping NS Prefix in Foundation   David Waite
    • [swift-evolution] Dropping NS Prefix in Foundation   Tony Parker
      • [swift-evolution] Dropping NS Prefix in Foundation   Patrick Smith
      • [swift-evolution] Dropping NS Prefix in Foundation   David Hart
      • [swift-evolution] Dropping NS Prefix in Foundation   Matthew Johnson
      • [swift-evolution] Dropping NS Prefix in Foundation   Tony Parker
      • [swift-evolution] Dropping NS Prefix in Foundation   Matthew Johnson
      • [swift-evolution] Dropping NS Prefix in Foundation   Tony Parker
      • [swift-evolution] Dropping NS Prefix in Foundation   Charles Srstka
      • [swift-evolution] Dropping NS Prefix in Foundation   David Waite
      • [swift-evolution] Dropping NS Prefix in Foundation   Josh Parmenter
      • [swift-evolution] Dropping NS Prefix in Foundation   Michael Sheaver
      • [swift-evolution] Dropping NS Prefix in Foundation   Patrick Smith
  • [swift-evolution] Dropping NS Prefix in Foundation   Rod Brown
• [swift-evolution] [Proposal] Memorization for running function only once   Muse M
• [swift-evolution] Standardize arguments in closures   João Nunes
• [swift-evolution] multi-line string literals.   ted van gaalen
  • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
    • [swift-evolution] multi-line string literals.   L. Mihalkovic
    • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   L. Mihalkovic
      • [swift-evolution] multi-line string literals.   Ricardo Parada
      • [swift-evolution] multi-line string literals.   Brent Royal-Gordon
• [swift-evolution] Dropping NS Prefix in Foundation   Jonathan Hull
  • [swift-evolution] Dropping NS Prefix in Foundation   Tony Parker
    • [swift-evolution] Dropping NS Prefix in Foundation   Patrick Smith
      • [swift-evolution] Dropping NS Prefix in Foundation   David Smith
    • [swift-evolution] Dropping NS Prefix in Foundation   Jonathan Hull
• [swift-evolution] [Pitch] Memos for Struct Calculated Properties   Jonathan Hull
  • [swift-evolution] [Pitch] Memos for Struct Calculated Properties   Wallacy
    • [swift-evolution] [Pitch] Memos for Struct Calculated Properties   Jonathan Hull
• [swift-evolution] [Pitch] alternative multiline string literals   L Mihalkovic
  • [swift-evolution] [Pitch] alternative multiline string literals   L Mihalkovic
• [swift-evolution] unums in Swift?   Matthew Johnson
• [swift-evolution] Proposal: Drop parentheses for initalization from tuple   Daniele Riccardelli
  • [swift-evolution] Proposal: Drop parentheses for initalization from tuple   Basem Emara
    • [swift-evolution] Proposal: Drop parentheses for initalization from tuple   Daniele Riccardelli
• [swift-evolution] Change in String.CharacterView.Index?   Joseph Bell
  • [swift-evolution] [swift-corelibs-dev] Change in String.CharacterView.Index?   Dennis Weissmann
• [swift-evolution] [Idea] Represent a point in time as a Swift immutable scalar type TimePoint   Steve Weller
• [swift-evolution] [Opinion] Thoughts about the SE-0025 (Scoped Access Level) proposal   Vanderlei Martinelli
  • [swift-evolution] [Opinion] Thoughts about the SE-0025 (Scoped Access Level) proposal   Ross O'Brien
• [swift-evolution] NSRange and Range   David Hart
• [swift-evolution] Typealiases in protocols and protocol extensions   David Hart

Last message date: Sun May 8 23:24:06 CDT 2016
Archived on: Sun May 8 23:28:11 CDT 2016

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