Re: [swift-evolution] [Pitch] #warning

+1 to #warning or optionally(?) emitting something like TODO: more visibly! In past ObjC projects, I have used #warning to confirm the right macros were enabled. I often (1) work around differences between the iOS simulator and device with TARGET_IPHONE_SIMULATOR (+similar) and (2) change API

Re: [swift-evolution] [Review] SE-0144: Allow Single Dollar Sign as a Valid Identifier

I’m a bit curious about how `$` is/would be used as a prefix operator! Perhaps I’m not creative :-( Regards, Will Stanton > On Oct 14, 2016, at 6:42 PM, Alex Martini via swift-evolution > wrote: > >> On Oct 14, 2016, at 1:53 PM, Hooman Mehr via swift-evolution >>

Re: [swift-evolution] SE-0144: Allow Single Dollar Sign as a Valid Identifier

> I’m a bit curious about how `$` is/would be used as a prefix operator! Clarifying: what type of operations would it be used for, and postfix too! Regards, Will Stanton ___ swift-evolution mailing list swift-evolution@swift.org

Re: [swift-evolution] [Review] SE-0144: Allow Single Dollar Sign as a Valid Identifier

> On Oct 21, 2016, at 10:48 PM, Jonathan S. Shapiro > <jonathan.s.shap...@gmail.com> wrote: > > On Fri, Oct 14, 2016 at 9:29 PM, Will Stanton via swift-evolution > <swift-evolution@swift.org> wrote: > I’m a bit curious about how `$` is/would be used as a pr

Re: [swift-evolution] [Proposal] Foundation Swift Encoders

Hello Itai, Thanks for your response and its explanations! Agreed that comprehension of multiple formats is important since there are a couple common ways of encoding JSON dates! Still, ISO 8601 appears pretty often (though I don’t have data on that, Stack Overflow says RFC 7493 I-JSON

Re: [swift-evolution] [Proposal] Foundation Swift Encoders

Hello, +1 This proposal seems helpful in standardizing how JSON objects can be written, and I commonly encode+decode JSON. The standard library JSON and PLIST encoders of Python are a strength, and Swift should be able to handle both formats just as easily. Still reading 'Swift Archival &

Re: [swift-evolution] [Pitch] Add an all algorithm to Sequence

+1 to adding, but the name `all` suggests (to me) the return of another sequence, not a Bool. Perhaps the function name should be question-like? Suggesting: `membersSatisfy(condition:)` or `allSatisfy(condition:)` or maybe even just `satisfies(condition:)` The question-like modifier/verb is

Re: [swift-evolution] class indent in swift, history?

Hello Chris, and all, Thanks for the replies and explanation! There have been moments when I felt like it would be nice if most functions could start at the 1-indent level. But I think I agree: true/consistent nesting is good motivation for the additional indent level. Still, in those times, I

[swift-evolution] class indent in swift, history?

Hello Chris and perhaps core team members, The comments on tab-levels for `switch` made me want to ask about the considerations that went into class and protocol-level indentation. Sorry if my wording isn’t precise, but in Objective-C, functions can (should) be at the same 0-indent level as