[swift-evolution] Discourse rollout re-schedule

Hi All- First of all, a big thank you to everyone who has provided feedback on our prototype Discourse forum. Based on the fact that we’re still receiving feedback, we’d like to move to a slightly less aggressive schedule for our rollout, in order to make sure that we’ve adequately addressed

Re: [swift-evolution] [swift-dev] Make offset index available for String

Sorry for my unclear "offset indexable". So what I mean by "offset indexable" is providing a "collection-element level offset indexing". This indexing could provide to any collection, because it is the basic concept of collections. The unicode offset is different than it and is important to

Re: [swift-evolution] Proposal and Timeline for Discourse Transition

Ok let’s keep it as is, and it is easy enough to add a new category if it appears to be useful. > On Dec 14, 2017, at 10:14 AM, John McCall wrote: > >> On Dec 14, 2017, at 1:11 PM, Jon Shier > > wrote: >> Personally I’d wait

Re: [swift-evolution] Proposal and Timeline for Discourse Transition

> On Dec 14, 2017, at 1:11 PM, Jon Shier wrote: > Personally I’d wait and see if much third party discussion happens and the > split it out if it gets too noisy. Otherwise you’re separating discussions > before we know they’ll happen. Yes, I've come around to this position,

Re: [swift-evolution] Proposal and Timeline for Discourse Transition

Personally I’d wait and see if much third party discussion happens and the split it out if it gets too noisy. Otherwise you’re separating discussions before we know they’ll happen. > On Dec 14, 2017, at 11:01 AM, John McCall via swift-evolution > wrote: > > >> On

Re: [swift-evolution] constant var

> On Dec 14, 2017, at 12:51 AM, Inder Kumar Rathore . > wrote: > > class MyClass { > private var myDict = [String : String]() > > func addMemebr() { > self.myDict["key"] = "value" // Ok for me > } > > func anotherFunc() { > self.myDict = [String :

Re: [swift-evolution] Proposal and Timeline for Discourse Transition

> On Dec 14, 2017, at 1:38 AM, Nicole Jacque wrote: > > Could you explain a bit more about how you think that category might be used > (vs. discussion) and organized? Well, I was thinking it could be a place for people to form stable working groups for various projects. I

Re: [swift-evolution] Optional Argument Chaining

Sent from my iPad On Dec 13, 2017, at 11:13 PM, Stephen Celis wrote: >> On Dec 13, 2017, at 9:53 PM, Erica Sadun wrote: >> >> Chris L had a beautiful solution for an "Unwrappable" protocol that allowed >> all of the optional sugar to be

Re: [swift-evolution] constant var

> 14 Dec. 2017 09:52 Inder Kumar Rathore . via swift-evolution > wrote: > > class MyClass { > private var myDict = [String : String]() > > func addMemebr() { > self.myDict["key"] = "value" // Ok for me > } > > func anotherFunc() { > self.myDict

Re: [swift-evolution] constant var

What are you going to do about this then? func thirdFunc() { self.myDict.removeAll() } Is this ok or not? Is it really different from `anotherFunc`? On Thu, Dec 14, 2017 at 10:52 AM, Inder Kumar Rathore . via swift-evolution wrote: > class

Re: [swift-evolution] constant var

> 14 Dec. 2017 17:52 Inder Kumar Rathore . via swift-evolution > wrote: > > class MyClass { > private var myDict = [String : String]() > > func addMemebr() { > self.myDict["key"] = "value" // Ok for me > } > > func anotherFunc() { > self.myDict

Re: [swift-evolution] constant var

class MyClass { private var myDict = [String : String]() func addMemebr() { self.myDict["key"] = "value" // Ok for me } func anotherFunc() { self.myDict = [String : String]() // Not okay for me, I don't want any code to do this within the class } } On Tue, Dec 12,

Re: [swift-evolution] Optional Argument Chaining

I do not feel new syntax is needed for this. You can do this currently: postfix operator ¿ extension Optional { struct UnwrapError: Error {} static postfix func ¿(_ value: Optional) throws -> Wrapped { if let value = value { return value } else {