Re: [swift-evolution] [Swift4] Mailing list vs. Forum

On 8/2/16 13:15, Karl Wagner via swift-evolution wrote: > There's no guarantee we would have to give it up entirely - many forum > platforms have apps with caching for offline viewing. > > Besides, im not sure these discussions are always so important that you > really need to download the entire

Re: [swift-evolution] [Swift4] Mailing list vs. Forum

On 8/2/16 12:21, Erica Sadun via swift-evolution wrote: > It is an instructive example of why remaining with a mailing list, flaws and > all, is probably the best answer for Swift Evolution. Whatever keeps a mailing list as bottom implementation gets my +1. Forums and other browser-based things

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0084: Allow trailing commas in parameter lists and tuples

On 5/12/16 10:52, Vladimir.S via swift-evolution wrote: > On 12.05.2016 16:22, Rainer Brockerhoff via swift-evolution wrote: >> I'm +1 on allowing either trailing commas *or* a line-break instead of >> where a comma is expected. >> >> Just as we allow a line-break wh

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0084: Allow trailing commas in parameter lists and tuples

On 5/11/16 14:29, Ricardo Parada via swift-evolution wrote: > Dropping the commas looks good and doesn't look like someone made a mistake. > I don't know what other implications / complications dropping the commas > would have but I like it. > >> On May 11, 2016, at 12:20 PM, Vladimir.S via

Re: [swift-evolution] Allow FloatLiteralType in FloatLiteralConvertible to be aliased to String

On 5/9/16 14:01, Joe Groff via swift-evolution wrote: > >> On May 8, 2016, at 10:30 PM, Morten Bek Ditlevsen wrote: >> >> This would be an excellent solution to the issue. >> Do you know if there are any existing plans for something like the >> DecimalLiteralConvertible? >

Re: [swift-evolution] multi-line string literals.

On 5/2/16 09:53, Brent Royal-Gordon via swift-evolution wrote: > When you are embedding enormous string literals in source code, you > must put undistorted representation of the string above all other > considerations. If the design which best permits the string to be >

Re: [swift-evolution] [Review] SE-0072: Fully eliminate implicit bridging conversions from Swift

On 4/29/16 21:32, Jordan Rose via swift-evolution wrote: > [Proposal: > https://github.com/apple/swift-evolution/blob/master/proposals/0072-eliminate-implicit-bridging-conversions.md] > > I’m a little concerned about the affect this has on “plist literals”. > Specifically, I can no longer

Re: [swift-evolution] Carriage Return in Collection Array Literal Initializer

On 4/28/16 00:00, Erica Sadun via swift-evolution wrote: >> On Apr 27, 2016, at 3:00 PM, Alex Martini via swift-evolution >> wrote: >> A comma is already allowed after the last element in an array or dictionary >> literal: > > And is very appreciated!! I wish the

Re: [swift-evolution] [swift-evolution-announce] [Review] SE-0067: Enhanced Floating Point Protocols

On 4/23/16 21:53, Brent Royal-Gordon via swift-evolution wrote: >> public protocol FloatingPoint: Comparable, IntegerLiteralConvertible { >> public protocol BinaryFloatingPoint: FloatingPoint, FloatLiteralConvertible { > > Any reason why FloatLiteralConvertible isn't on FloatingPoint? While I'm

Re: [swift-evolution] [Proposal] Custom operators

Chris, thanks for commenting, but see below: On 4/9/16 10:33, Chris Lattner via swift-evolution wrote: >> On Apr 8, 2016, at 5:16 AM, Rainer Brockerhoff via swift-evolution >> <swift-evolution@swift.org> wrote: >>> - I definitely agree that a partial ordering

Re: [swift-evolution] [Proposal] Custom operators

On 4/8/16 02:59, Chris Lattner via swift-evolution wrote: >> On Apr 7, 2016, at 1:39 PM, Антон Жилин via swift-evolution >> wrote: >> Link for newcomers: >> https://github.com/Anton3/swift-evolution/blob/operator-precedence/proposals/-operator-precedence.md >> >>

Re: [swift-evolution] [Proposal] Custom operators

On 4/4/16 15:21, Daniel Duan via swift-evolution wrote: >> Антон Жилин via swift-evolution writes: >> >> Swift 2.2 is out, and I restart discussion on syntax for custom operators. >> I insist that this time we should focus less on linguistic aspects. > ...[snip] > > 3. It

Re: [swift-evolution] Feature proposal: Range operator with step

On 3/31/16 15:29, Stephen Canon via swift-evolution wrote: > >> On Mar 31, 2016, at 11:16 AM, Rainer Brockerhoff via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> On 3/31/16 15:06, Dave Abrahams via swift-evolution wrote: >>>... >

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

(replying on gmane as I see my previous reply lost threading. @#$%^ Thunderbird.) On 3/24/16 11:31, Stephen Canon via swift-evolution wrote: >> On Mar 24, 2016, at 10:01 AM, Rainer Brockerhoff >> wrote: >> >> There's the mismatch between decimal representation of binary

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

On 3/24/16 09:54, Stephen Canon wrote: > On Mar 23, 2016, at 5:26 AM, Rainer Brockerhoff via swift-evolution > <swift-evolution@swift.org> wrote: ... >> On 3/22/16 23:20, Michael Gottesman via swift-evolution wrote: >>>> Pre-proposal: Safer Decimal Calculation

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

On 3/22/16 23:20, Michael Gottesman via swift-evolution wrote: > >> On Mar 18, 2016, at 3:42 PM, Rainer Brockerhoff via swift-evolution >> <swift-evolution@swift.org> wrote: >> >> First draft towards a tentative pre-proposal: >> https://gist.githu

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

On 3/20/16 14:43, Andrey Tarantsov via swift-evolution wrote: > I have no stake in this proposal, except for: > >> I suggest, therefore, that this acceptance be indicated by an >> annotation to the literal; a form such as ~0.1 might be easiest to >> read and implement, as the prefix ~ operator

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

On 3/19/16 09:03, Tino Heth via swift-evolution wrote: >> Just wanted to expand on the type tolerances idea with an example: >> >> let a:Float±0.1 = 1234.56 >> let b:Float±0.5 = 123.456 >> >> let result:Float±0.25 = a + b // Error as b’s tolerance > 0.25 > That example is a good motivation for two

Re: [swift-evolution] Pre-proposal: Safer Decimal Calculations

On 3/18/16 21:00, Dany St-Amant via swift-evolution wrote: > >> Le 18 mars 2016 à 18:42, Rainer Brockerhoff via swift-evolution >> <swift-evolution@swift.org> a écrit : >> >> First draft towards a tentative pre-proposal: >> https://gist.githu

[swift-evolution] Pre-proposal: Safer Decimal Calculations

First draft towards a tentative pre-proposal: https://gist.github.com/rbrockerhoff/6874a5698bb479886e83 -- Pre-proposal: Safer Decimal Calculations Proposal: TBD Author(s): Rainer Brockerhoff Status: TBD Review manager: TBD Quoting the “The Swift Programming Language” book: “Swift adopts

Re: [swift-evolution] Proposal: Python's indexing and slicing

On 23/12/15 12:45 , swift-evolution-requ...@swift.org wrote: > Date: Tue, 22 Dec 2015 21:12:08 -0800 From: Kevin Ballard > To: Jordan Rose Message-ID: > <1450847528.263398.474637513.2f478...@webmail.messagingengine.com> > > Oh that's a good point, I hadn't

Re: [swift-evolution] ternary operator ?: suggestion

On 22/12/15 16:50 , swift-evolution-requ...@swift.org wrote: > Date: Tue, 22 Dec 2015 10:07:26 -0800 > From: Jordan Rose > To: Thorsten Seitz > Message-ID: <2d35f5bd-3ddf-43c3-a461-14fb65530...@apple.com> > > I think this is a good point. We