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

2017-12-13 Thread Nicole Jacque via swift-evolution
Could you explain a bit more about how you think that category might be used (vs. discussion) and organized? > On Dec 13, 2017, at 9:58 PM, John McCall via swift-evolution > wrote: > >> On Dec 13, 2017, at 6:00 PM, Jonathan Hull via swift-evolution >> mailto:swift-evolution@swift.org>> wrote:

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

2017-12-13 Thread Nicole Jacque via swift-evolution
Ok, I’m certainly not opposed to adding a subcategory to “Swift Users” for this if we think it’s useful. > On Dec 13, 2017, at 3:00 PM, Jonathan Hull via swift-evolution > wrote: > > I would also like a place in the “Using Swift” for working on libraries or > open source projects. I think ask

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

2017-12-13 Thread John McCall via swift-evolution
> On Dec 13, 2017, at 6:00 PM, Jonathan Hull via swift-evolution > wrote: > I would also like a place in the “Using Swift” for working on libraries or > open source projects. I think asking for collaborators is fundamentally > different than asking technical questions. > > It would be nice to

Re: [swift-evolution] Optional Argument Chaining

2017-12-13 Thread Stephen Celis via swift-evolution
> 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 extended to any type that had a biased > `Wrapped` item, allowing it to be used with `Either`, `Wrapped`, etc as well > as form th

Re: [swift-evolution] Optional Argument Chaining

2017-12-13 Thread Erica Sadun via swift-evolution
> On Dec 13, 2017, at 10:20 AM, Stephen Celis via swift-evolution > wrote: > >> On Dec 11, 2017, at 1:08 PM, Matthew Johnson via swift-evolution >> wrote: >> >> It’s worth mentioning that the problem this thread is discussing can be >> generalized to idioms / applicative. The specific cas

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

2017-12-13 Thread Jonathan Hull via swift-evolution
I would also like a place in the “Using Swift” for working on libraries or open source projects. I think asking for collaborators is fundamentally different than asking technical questions. It would be nice to have support somehow for the idea of working groups for evolution > On Dec 12, 2017

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

2017-12-13 Thread Dave Abrahams via swift-evolution
Sent from my iPhone > On Dec 12, 2017, at 12:29 PM, Alejandro Martinez via swift-evolution > wrote: > > Yes that's what I was suggesting. > My view is that different kind of conversations would happen in a > "help" vs. "announcements" category. Some people may be interested in > being up to d

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

2017-12-13 Thread Nicole Jacque via swift-evolution
Thanks for the JIRAs — I’m posting updates there! > On Dec 11, 2017, at 11:41 PM, Ben Rimmington wrote: > > [Forum] merging multiple staged accounts > > > [Forum] importing names with non-Latin characters > > > --

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

2017-12-13 Thread Nicole Jacque via swift-evolution
We’ve tried to avoid having too many categories, and the hope is that something like this can be accomplished by using tags. That said, if we find that that does not work well, or that we get enough of these sort of topics, we can easily create a new category for them. > On Dec 12, 2017, at 12

Re: [swift-evolution] Optional Argument Chaining

2017-12-13 Thread Stephen Celis via swift-evolution
> On Dec 11, 2017, at 1:08 PM, Matthew Johnson via swift-evolution > wrote: > > It’s worth mentioning that the problem this thread is discussing can be > generalized to idioms / applicative. The specific case here is for Optional > but many other types could benefit from an elegant syntactic

Re: [swift-evolution] Optional Argument Chaining

2017-12-13 Thread Jonathan Hull via swift-evolution
+1 to this. I also like Adrian’s notation where the ? is after the name, but before the parameter list. > On Dec 12, 2017, at 7:33 AM, Yuta Koshizawa via swift-evolution > wrote: > > I think evaluating them in the same way as `try` calls is consistent. > > ``` > f(g()?, h()?, i(), j()?)? > /