December 2015 Archives by thread

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

Starting: Thu Dec 3 13:52:48 CST 2015
Ending: Sat Dec 5 12:52:22 CST 2015
Messages: 411

• [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Zef Houssney
  • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   David Hart
    • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Zef Houssney
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Kevin Ballard
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Chris Lattner
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   David Waite
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Sean Heber
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Zef Houssney
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Dan Appel
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Sean Heber
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Kevin Ballard
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   John McCall
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Chris Lattner
      • [swift-evolution] Proposal: Optional Binding Shorthand Syntax   Chris Lattner
• [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
  • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Gregory Casamento
    • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   David Hart
    • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   David Hart
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Gregory Casamento
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Gregory Casamento
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   David Hart
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
      • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
  • [swift-evolution] Proposal: Swift Open Source Project and Foundation replacements   Adrian Kashivskyy
  • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Chris Lattner
    • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Jacob Bandes-Storch
      • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Tony Parker
    • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
• [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Dan Stenmark
  • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Douglas Gregor
    • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   David Hart
    • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Alex Migicovsky
      • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Sean Heber
      • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Vinicius Vendramini
      • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Dan Stenmark
      • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Sean Heber
      • [swift-evolution] API Guidelines for Asynchronous Completion Handlers?   Stephen Celis
• [swift-evolution] KVO/KVC in Swift   Colin Cornaby
  • [swift-evolution] KVO/KVC in Swift   Chris Lattner
    • [swift-evolution] KVO/KVC in Swift   Adrian Kashivskyy
• [swift-evolution] Expanded support for numeric types in stdlib?   Austin Zheng
  • [swift-evolution] Expanded support for numeric types in stdlib?   Chris Lattner
  • [swift-evolution] Expanded support for numeric types in stdlib?   Dmitri Gribenko
    • [swift-evolution] Expanded support for numeric types in stdlib?   Austin Zheng
      • [swift-evolution] Expanded support for numeric types in stdlib?   Austin Zheng
      • [swift-evolution] Expanded support for numeric types in stdlib?   Dmitri Gribenko
      • [swift-evolution] Expanded support for numeric types in stdlib?   Kevin Ballard
      • [swift-evolution] Expanded support for numeric types in stdlib?   Austin Zheng
      • [swift-evolution] Expanded support for numeric types in stdlib?   Vinicius Vendramini
• [swift-evolution] Proposal for generic protocols   Tal Atlas
  • [swift-evolution] Proposal for generic protocols   David Hart
    • [swift-evolution] Proposal for generic protocols   Kevin Ballard
  • [swift-evolution] Proposal for generic protocols   Joe Groff
    • [swift-evolution] Proposal for generic protocols   Tal Atlas
      • [swift-evolution] Proposal for generic protocols   Joe Groff
      • [swift-evolution] Proposal for generic protocols   Ken Ferry
      • [swift-evolution] Proposal for generic protocols   Ken Ferry
      • [swift-evolution] Proposal for generic protocols   Ken Ferry
• [swift-evolution] Idea for declaring expected types and value ranges   Sean Heber
  • [swift-evolution] Idea for declaring expected types and value ranges   Adrian Kashivskyy
    • [swift-evolution] Idea for declaring expected types and value ranges   Jacob Bandes-Storch
    • [swift-evolution] Idea for declaring expected types and value ranges   Sean Heber
• [swift-evolution] Change the name of the boolean operators?   Sean Heber
  • [swift-evolution] Change the name of the boolean operators?   Chris Lattner
• [swift-evolution] KVO/KVC in Swift   Colin Cornaby
• [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Jacob Bandes-Storch
  • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Tony Parker
    • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
• [swift-evolution] Proposal: Sealed protocols   Felix Gabel
  • [swift-evolution] Proposal: Sealed protocols   Douglas Gregor
    • [swift-evolution] Proposal: Sealed protocols   Mehdi Amini
      • [swift-evolution] Proposal: Sealed protocols   Douglas Gregor
      • [swift-evolution] Proposal: Sealed protocols   Mehdi Amini
    • [swift-evolution] Proposal: Sealed protocols   Dmitri Gribenko
      • [swift-evolution] Proposal: Sealed protocols   Anandabits
      • [swift-evolution] Proposal: Sealed protocols   Joe Groff
      • [swift-evolution] Proposal: Sealed protocols   Felix Gabel
      • [swift-evolution] Proposal: Sealed protocols   Adrian Kashivskyy
  • [swift-evolution] Proposal: Sealed protocols   Kevin Ballard
  • [swift-evolution] Proposal: Sealed protocols   Joe Groff
    • [swift-evolution] Proposal: Sealed protocols   Felix Gabel
• [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Amir Michail
  • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Chris Lattner
    • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Amir Michail
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Per Melin
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Chris Lattner
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Jon Shier
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Игорь Хмурец
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Chris Lattner
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Per Melin
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Chris Lattner
      • [swift-evolution] Please remove obscure "!" requirements for implicitly unwrapped optionals   Per Melin
• [swift-evolution] If-let Shortcut Syntax   Richard Fox
  • [swift-evolution] If-let Shortcut Syntax   Adrian Kashivskyy
• [swift-evolution] SwiftScript   Dave Thornton
  • [swift-evolution] SwiftScript   Chris Lattner
    • [swift-evolution] SwiftScript   David Owens II
• [swift-evolution] C-style For Loops   Erica Sadun
  • [swift-evolution] C-style For Loops   Chris Lattner
  • [swift-evolution] C-style For Loops   Douglas Gregor
    • [swift-evolution] C-style For Loops   David Smith
    • [swift-evolution] C-style For Loops   Keith Smiley
      • [swift-evolution] C-style For Loops   Andy Matuschak
      • [swift-evolution] C-style For Loops   Eric Chamberlain
      • [swift-evolution] C-style For Loops   Kevin Ballard
      • [swift-evolution] C-style For Loops   Sean Heber
      • [swift-evolution] C-style For Loops   ChanMaxthon
      • [swift-evolution] C-style For Loops   Kevin Ballard
      • [swift-evolution] C-style For Loops   Erica Sadun
      • [swift-evolution] C-style For Loops   Joe Groff
      • [swift-evolution] C-style For Loops   Douglas Gregor
      • [swift-evolution] C-style For Loops   Ray Fix
      • [swift-evolution] C-style For Loops   Alex Chan
• [swift-evolution] SwiftScript   Constantino Tsarouhas
• [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Amir Michail
  • [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Jacob Bandes-Storch
    • [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Kevin Ballard
      • [swift-evolution] ? suffix for <, >, <=, >= comparisons with optionals to prevent subtle bugs   Jacob Bandes-Storch
• [swift-evolution] Revisiting Optionals as Sequences   Developer
• [swift-evolution] Pluggable hash algorithm for containers   Ray Fix
  • [swift-evolution] Pluggable hash algorithm for containers   Dmitri Gribenko
    • [swift-evolution] Pluggable hash algorithm for containers   Ray Fix
      • [swift-evolution] Pluggable hash algorithm for containers   Dmitri Gribenko
• [swift-evolution] You should be able to label a 1-tuple return value as a way to document the return value.   Amir Michail
• [swift-evolution] if case 1, 2, 3 = x { ... } results in error in swift 2   Amir Michail
  • [swift-evolution] if case 1, 2, 3 = x { ... } results in error in swift 2   Adrian Kashivskyy
  • [swift-evolution] if case 1, 2, 3 = x { ... } results in error in swift 2   Kevin Ballard
    • [swift-evolution] if case 1, 2, 3 = x { ... } results in error in swift 2   Amir Michail
      • [swift-evolution] if case 1, 2, 3 = x { ... } results in error in swift 2   Kevin Ballard
• [swift-evolution] Proposal: Typed throws   Adrian Kashivskyy
  • [swift-evolution] Proposal: Typed throws   Adrian Kashivskyy
    • [swift-evolution] Proposal: Typed throws   John McCall
      • [swift-evolution] Proposal: Typed throws   Matthew Johnson
      • [swift-evolution] Proposal: Typed throws   David Owens II
      • [swift-evolution] Proposal: Typed throws   John McCall
      • [swift-evolution] Proposal: Typed throws   David Owens II
      • [swift-evolution] Proposal: Typed throws   David Owens II
      • [swift-evolution] Proposal: Typed throws   John McCall
      • [swift-evolution] Proposal: Typed throws   Chris Lattner
• [swift-evolution] NDAs, Open Source, and the Iron Curtain   Erica Sadun
  • [swift-evolution] NDAs, Open Source, and the Iron Curtain   Chris Lattner
• [swift-evolution] Proposal : Introduction of System Defined UI Variables - ScreenSize, IsPad.   Tarun Tyagi
  • [swift-evolution] Proposal : Introduction of System Defined UI Variables - ScreenSize, IsPad.   David Smith
• [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
  • [swift-evolution] ternary operator ?: suggestion   Dan Appel
    • [swift-evolution] ternary operator ?: suggestion   Sean Heber
      • [swift-evolution] ternary operator ?: suggestion   David Hart
      • [swift-evolution] ternary operator ?: suggestion   David Waite
      • [swift-evolution] ternary operator ?: suggestion   Sean Heber
      • [swift-evolution] ternary operator ?: suggestion   Adrian Kashivskyy
      • [swift-evolution] ternary operator ?: suggestion   David Owens II
      • [swift-evolution] ternary operator ?: suggestion   David Hart
      • [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
      • [swift-evolution] ternary operator ?: suggestion   J. Cheyo Jimenez
      • [swift-evolution] ternary operator ?: suggestion   Chris Lattner
• [swift-evolution] More verbose logical operators   Bee
  • [swift-evolution] More verbose logical operators   Keith Smiley
    • [swift-evolution] More verbose logical operators   Bee
• [swift-evolution] swift for ios?   Bee
  • [swift-evolution] swift for ios?   Adrian Kashivskyy
    • [swift-evolution] swift for ios?   Bee
  • [swift-evolution] swift for ios?   Douglas Gregor
• [swift-evolution] Idea for enabling DSLs: bind to self in closures   David Waite
  • [swift-evolution] Idea for enabling DSLs: bind to self in closures   Joe Groff
    • [swift-evolution] Idea for enabling DSLs: bind to self in closures   David Waite
      • [swift-evolution] Idea for enabling DSLs: bind to self in closures   Stephen Celis
    • [swift-evolution] Idea for enabling DSLs: bind to self in closures   Kevin Ballard
      • [swift-evolution] Idea for enabling DSLs: bind to self in closures   David Waite
• [swift-evolution] General take on "special" code in Swift   Timothy Wood
  • [swift-evolution] General take on "special" code in Swift   Chris Lattner
• [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   David Hart
  • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   ChanMaxthon
    • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Alex Blewitt
      • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
      • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
      • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Adrian Kashivskyy
      • [swift-evolution] [swift-corelibs-dev] Proposal: Swift Open Source Project and Foundation replacements   Maxthon Chan
• [swift-evolution] abstract keyWord proposal   David Scrève
  • [swift-evolution] abstract keyWord proposal   T.J. Usiyan
    • [swift-evolution] abstract keyWord proposal   David Scrève
      • [swift-evolution] abstract keyWord proposal   T.J. Usiyan
      • [swift-evolution] abstract keyWord proposal   David Scrève
      • [swift-evolution] abstract keyWord proposal   Tal Atlas
      • [swift-evolution] abstract keyWord proposal   Vinicius Vendramini
• [swift-evolution] Generic `typealias`s   Dapeng Gao
  • [swift-evolution] Generic `typealias`s   T.J. Usiyan
  • [swift-evolution] Generic `typealias`s   Chris Lattner
  • [swift-evolution] Generic `typealias`s   Joe Groff
    • [swift-evolution] Generic `typealias`s   Kevin Ballard
    • [swift-evolution] Generic `typealias`s   Douglas Gregor
      • [swift-evolution] Generic `typealias`s   Austin Zheng
      • [swift-evolution] Generic `typealias`s   Austin Zheng
• [swift-evolution] Control Flow Expressions   Sergey Shulepov
  • [swift-evolution] Control Flow Expressions   Maxthon Chan
    • [swift-evolution] Control Flow Expressions   Sergey Shulepov
    • [swift-evolution] Control Flow Expressions   Joe Groff
  • [swift-evolution] Control Flow Expressions   J. Cheyo Jimenez
  • [swift-evolution] Control Flow Expressions   J. Cheyo Jimenez
    • [swift-evolution] Control Flow Expressions   Jonathan Hull
      • [swift-evolution] Control Flow Expressions   Jonathan Hull
      • [swift-evolution] Control Flow Expressions   David Hart
  • [swift-evolution] Control Flow Expressions   Chris Lattner
• [swift-evolution] Proposal: Access control for protocols   Adrian Zubarev
• [swift-evolution] SE-0005: Ambiguous NS prefix removals   Brent Royal-Gordon
  • [swift-evolution] SE-0005: Ambiguous NS prefix removals   Tony Parker
    • [swift-evolution] SE-0005: Ambiguous NS prefix removals   Brent Royal-Gordon
      • [swift-evolution] SE-0005: Ambiguous NS prefix removals   Nikolai Vazquez
      • [swift-evolution] SE-0005: Ambiguous NS prefix removals   Tony Parker
      • [swift-evolution] SE-0005: Ambiguous NS prefix removals   Rudolf Adamkovic
• [swift-evolution] lazy keyword vs lazy initialization pattern   David Hart
  • [swift-evolution] lazy keyword vs lazy initialization pattern   Cole Kurkowski
• [swift-evolution] Proposal: CustomConvertible protocol   Adrian Zubarev
  • [swift-evolution] Proposal: CustomConvertible protocol   Stepan Hruda
  • [swift-evolution] Proposal: CustomConvertible protocol   John McCall
• [swift-evolution] Fw: Re: Proposal: CustomConvertible protocol   Adrian Zubarev
  • [swift-evolution] Proposal: CustomConvertible protocol   Jeremy Pereira
• [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Amir Michail
  • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   J. Cheyo Jimenez
    • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Amir Michail
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   David Waite
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Sean Heber
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Amir Michail
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Alex Blewitt
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Amir Michail
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Adrian Kashivskyy
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Amir Michail
      • [swift-evolution] mandatory "?" suffix for identifiers associated with optional types   Adrian Kashivskyy
• [swift-evolution] Proposal: Protocol methods should accept default arguments   Ben
  • [swift-evolution] Proposal: Protocol methods should accept default arguments   Felix Gabel
    • [swift-evolution] Proposal: Protocol methods should accept default arguments   Ben
  • [swift-evolution] Proposal: Protocol methods should accept default arguments   Sean Heber
• [swift-evolution] Allow Selectors to be used as Closures   Chris Byatt
  • [swift-evolution] Allow Selectors to be used as Closures   Cole Kurkowski
    • [swift-evolution] Allow Selectors to be used as Closures   David Smith
      • [swift-evolution] Allow Selectors to be used as Closures   Joe Groff
  • [swift-evolution] Allow Selectors to be used as Closures   Jorge Bernal
• [swift-evolution] Ability to set access control independently for getter & setter of a property   Evan Maloney
  • [swift-evolution] Ability to set access control independently for getter & setter of a property   Jordan Rose
    • [swift-evolution] Ability to set access control independently for getter & setter of a property   Evan Maloney
      • [swift-evolution] Ability to set access control independently for getter & setter of a property   Johan Jensen
• [swift-evolution] Proposal: Optional unwrap resulting in exception.   Nikolay Petrov
• [swift-evolution] Process question: breaking proposals for API changes to stdlib?   Andy Matuschak
  • [swift-evolution] Process question: breaking proposals for API changes to stdlib?   Douglas Gregor
• [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   plx
  • [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   John McCall
    • [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   plx
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
  • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Smith
  • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Rudolf Adamkovic
    • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Rudolf Adamkovič
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Stephen Celis
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Stephen Celis
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Kevin Ballard
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Stephen Celis
• [swift-evolution] Request for Discussion: Setup closures   Erica Sadun
  • [swift-evolution] Request for Discussion: Setup closures   Joe Groff
    • [swift-evolution] Request for Discussion: Setup closures   Sean Heber
      • [swift-evolution] Request for Discussion: Setup closures   Erica Sadun
      • [swift-evolution] Request for Discussion: Setup closures   crk at fastmail.com
      • [swift-evolution] Request for Discussion: Setup closures   Anandabits
      • [swift-evolution] Request for Discussion: Setup closures   Michel Fortin
      • [swift-evolution] Request for Discussion: Setup closures   Erica Sadun
      • [swift-evolution] Request for Discussion: Setup closures   Sean Heber
      • [swift-evolution] Request for Discussion: Setup closures   David Waite
      • [swift-evolution] Request for Discussion: Setup closures   Gaelan Bright Steele
    • [swift-evolution] Request for Discussion: Setup closures   Kevin Ballard
  • [swift-evolution] Request for Discussion: Setup closures   Anandabits
• [swift-evolution] Proposal: Remove the "fallthrough" keyword   jalkut at red-sweater.com
  • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Erica Sadun
    • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Greg Titus
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Ray Fix
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Ray Fix
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Erica Sadun
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Kevin Ballard
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   John McCall
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Kevin Ballard
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   John Calsbeek
  • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Sean Heber
    • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Kevin Ballard
  • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Andy Matuschak
  • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Chris Lattner
    • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Pierre Habouzit
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Vinicius Vendramini
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   David Owens II
      • [swift-evolution] Proposal: Remove the "fallthrough" keyword   Pierre Habouzit
• [swift-evolution] Proposal: Bridging for Swift Structs in Objective-C   Dan Stenmark
  • [swift-evolution] Proposal: Bridging for Swift Structs in Objective-C   Jean-Daniel Dupas
    • [swift-evolution] Proposal: Bridging for Swift Structs in Objective-C   Dan Stenmark
  • [swift-evolution] Proposal: Bridging for Swift Structs in Objective-C   Chris Lattner
• [swift-evolution] Type-safe selectors   Michel Fortin
  • [swift-evolution] Type-safe selectors   Joe Groff
    • [swift-evolution] Type-safe selectors   Joe Groff
      • [swift-evolution] Type-safe selectors   John McCall
      • [swift-evolution] Type-safe selectors   Michel Fortin
    • [swift-evolution] Type-safe selectors   Michel Fortin
      • [swift-evolution] Type-safe selectors   Joe Groff
    • [swift-evolution] Type-safe selectors   Kevin Ballard
      • [swift-evolution] Type-safe selectors   Joe Groff
      • [swift-evolution] Type-safe selectors   Michel Fortin
      • [swift-evolution] Type-safe selectors   Kevin Ballard
      • [swift-evolution] Type-safe selectors   Brent Royal-Gordon
      • [swift-evolution] Type-safe selectors   Michel Fortin
      • [swift-evolution] Type-safe selectors   Joe Groff
      • [swift-evolution] Type-safe selectors   Michel Fortin
      • [swift-evolution] Type-safe selectors   Joe Groff
      • [swift-evolution] Type-safe selectors   Michel Fortin
      • [swift-evolution] Type-safe selectors   Brent Royal-Gordon
      • [swift-evolution] Type-safe selectors   Michel Fortin
• [swift-evolution] C-style For Loops   Colin Cornaby
  • [swift-evolution] C-style For Loops   Joe Groff
    • [swift-evolution] C-style For Loops   Johan Jensen
• [swift-evolution] Lazy flatMap for Optionals   Donnacha Oisín Kidney
  • [swift-evolution] Lazy flatMap for Optionals   Dmitri Gribenko
• [swift-evolution] Failable arithmetic   Brent Royal-Gordon
  • [swift-evolution] Failable arithmetic   Chris Lattner
    • [swift-evolution] Failable arithmetic   Joe Groff
    • [swift-evolution] Failable arithmetic   Brent Royal-Gordon
• [swift-evolution] Type information containing multiple additional protocols   Daniel Muhra
  • [swift-evolution] Type information containing multiple additional protocols   Jacob Bandes-Storch
• [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   Tal Atlas
  • [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   Dan Appel
    • [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   Matthew Johnson
      • [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   crk at fastmail.com
      • [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   Tal Atlas
      • [swift-evolution] Proposal: helpers for initializing properties of same name as parameters   Matthew Johnson
• [swift-evolution] C-style For Loops   Colin Cornaby
  • [swift-evolution] C-style For Loops   Tyler Cloutier
    • [swift-evolution] C-style For Loops   Roland King
      • [swift-evolution] C-style For Loops   Matthijs Hollemans
      • [swift-evolution] C-style For Loops   Per Melin
      • [swift-evolution] C-style For Loops   Tyler Cloutier
      • [swift-evolution] C-style For Loops   Roland King
      • [swift-evolution] C-style For Loops   Thorsten Seitz
      • [swift-evolution] C-style For Loops   Michel Fortin
• [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Andy Matuschak
  • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Kevin Ballard
    • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Dmitri Gribenko
      • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Kevin Ballard
      • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Dmitri Gribenko
      • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Maxwell Swadling
      • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Dmitri Gribenko
      • [swift-evolution] Reconsidering the (Element -> T?) variant of SequenceType.flatMap   Maxwell Swadling
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Colin Cornaby
  • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Kevin Ballard
    • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Jon Shier
    • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Tyler Cloutier
      • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Amir Michail
  • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Adrian Kashivskyy
    • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Amir Michail
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Austin Zheng
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Amir Michail
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Austin Zheng
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Paul Young
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Harlan Haskins
      • [swift-evolution] "bad smells" should be compiler errors with suggestions on how to fix them   Adrian Kashivskyy
• [swift-evolution] Type Inferencing For Error Handling (try catch blocks)   Manav Gabhawala
  • [swift-evolution] Type Inferencing For Error Handling (try catch blocks)   John McCall
    • [swift-evolution] Type Inferencing For Error Handling (try catch blocks)   Adrian Kashivskyy
      • [swift-evolution] Type Inferencing For Error Handling (try catch blocks)   Jean-Daniel Dupas
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Michael Buckley
• [swift-evolution] lazy keyword vs lazy initialization pattern   Cameron Knight
  • [swift-evolution] lazy keyword vs lazy initialization pattern   Kevin Ballard
• [swift-evolution] Extending Failable Initializers   Manav Gabhawala
  • [swift-evolution] Extending Failable Initializers   Brent Royal-Gordon
    • [swift-evolution] Extending Failable Initializers   Kevin Ballard
• [swift-evolution] Idea for declaring expected types and value ranges   Jaden Geller
• [swift-evolution] fcntl() should be added to the standard library.   Bill Abt
• [swift-evolution] Proposal: More Command-line Compatibilities   Stark Shaw
• [swift-evolution] Revisiting Optionals as Sequences   Harlan Haskins
  • [swift-evolution] Revisiting Optionals as Sequences   Developer
  • [swift-evolution] Revisiting Optionals as Sequences   Kevin Ballard
• [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   Harlan Haskins
  • [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   plx
    • [swift-evolution] Proposal: Automatic Wrapper Synthesis / "deriving"   Matthew Johnson
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions (David Hart)   Yichen Cao
• [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Dan
  • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   Maxthon Chan
    • [swift-evolution] Proposal: Re-instate mandatory self for accessing instance properties and functions   David Hart
• [swift-evolution] Proposal: weakStrong self in completion handler closures   Robert Vojta
• [swift-evolution] Proposal: Auto-convert for numbers when safe   Jonathan Hull
  • [swift-evolution] Proposal: Auto-convert for numbers when safe   Pyry Jahkola
  • [swift-evolution] Proposal: Auto-convert for numbers when safe   Brent Royal-Gordon
• [swift-evolution] "if case" syntax is ugly   Amir Michail
  • [swift-evolution] "if case" syntax is ugly   Chris Lattner
• [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   T.J. Usiyan
  • [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Anandabits
  • [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Per Melin
  • [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Joe Groff
    • [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   T.J. Usiyan
      • [swift-evolution] Proposal: Tail Call Optimization keyword/attribute   Joe Groff
• [swift-evolution] Proposal: Finalization in protocol extensions and default implementations   Adrian Zubarev
• [swift-evolution] Proposal: floating point static min / max properties   Matthew Johnson
  • [swift-evolution] Proposal: floating point static min / max properties   Stephen Canon
    • [swift-evolution] Proposal: floating point static min / max properties   John Calsbeek
• [swift-evolution] reinitializing part of an object where calling super.init is optional   Amir Michail
• [swift-evolution] C-style For Loops   Roland King
  • [swift-evolution] C-style For Loops   Tyler Cloutier
• [swift-evolution] ternary operator ?: suggestion   possen p
• [swift-evolution] Redundant parentheses should result in compile errors.   Amir Michail
  • [swift-evolution] Redundant parentheses should result in compile errors.   Adrian Kashivskyy
  • [swift-evolution] Redundant parentheses should result in compile errors.   Nicky Gerritsen
    • [swift-evolution] Redundant parentheses should result in compile errors.   Adrian Kashivskyy
      • [swift-evolution] Redundant parentheses should result in compile errors.   Amir Michail
      • [swift-evolution] Redundant parentheses should result in compile errors.   Adrian Kashivskyy
      • [swift-evolution] Redundant parentheses should result in compile errors.   John Calsbeek

Last message date: Sat Dec 5 12:52:22 CST 2015
Archived on: Sat Dec 5 12:53:09 CST 2015

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