Re: [swift-evolution] Feedback on SE-0166 and SE-0167

Excellent! Glad that ended up working out — looking forward to seeing this improve quality of life for GRDB users and others. :) On 27 May 2017, at 3:40, Gwendal Roué wrote: > Le 27 mai 2017 à 11:59, David Hart a écrit : I didn’t know that was possible either! Really

Re: [swift-evolution] Revisiting SE-0110

on Thu May 25 2017, Gwendal Roué wrote: >> Furthermore, this probably comes up most commonly with dictionaries, >> since they're a sequence of tuples. The element tuple for >> dictionaries has element labels (key: Key, value: Value), so instead >> of writing `{ tuple

[swift-evolution] Pitch: String Index Overhaul

Pretty version: https://github.com/dabrahams/swift-evolution/blob/string-index-overhaul/proposals/-string-index-overhaul.md # String Index Overhaul * Proposal: [SE-](-string-index-overhaul.md) * Authors: [Dave Abrahams](https://github.com/dabrahams) * Review Manager: TBD *

Re: [swift-evolution] Feedback on SE-0166 and SE-0167

> On 27 May 2017, at 12:40, Gwendal Roué wrote: > > >> Le 27 mai 2017 à 11:59, David Hart > > a écrit : >> >> I didn’t know that was possible either! Really cool. Even better: >> >> if let databaseValueType = T.self as?

Re: [swift-evolution] Revisiting SE-0110

> Le 27 mai 2017 à 14:20, Gwendal Roué a écrit : > >> Le 26 mai 2017 à 21:35, Robert Bennett via swift-evolution >> > a écrit : >> >> On the contrary I think the solution can absolutely be to break other code.

Re: [swift-evolution] Revisiting SE-0110

> Le 26 mai 2017 à 21:35, Robert Bennett via swift-evolution > a écrit : > > On the contrary I think the solution can absolutely be to break other code. You can break whatever you want. But whatever the solution you come up with, remember that SE-0110 currently

Re: [swift-evolution] Revisiting SE-0110

Regarding the requiring of parentheses for arguments in closures: I'd suggest to look into SE-0066's paragraph "Should we require parentheses in closure expression parameter lists?" and "Rationale" for this SE: https://lists.swift.org/pipermail/swift-evolution-announce/2016-May/000138.html

Re: [swift-evolution] Feedback on SE-0166 and SE-0167

> Le 27 mai 2017 à 11:59, David Hart a écrit : > > I didn’t know that was possible either! Really cool. Even better: > > if let databaseValueType = T.self as? DatabaseValueConvertible.Type { > let databaseValue: DatabaseValue = row.value(named: key.stringValue) >

Re: [swift-evolution] Revisiting SE-0110

> On 26 May 2017, at 20:35, Robert Bennett via swift-evolution > wrote: > > On the contrary I think the solution can absolutely be to break other code. > Allowing no parentheses is not a very useful shorthand -- it only saves two > characters -- and with SE-0110

Re: [swift-evolution] Feedback on SE-0166 and SE-0167

> On 27 May 2017, at 08:59, Gwendal Roué wrote: > > >> Le 26 mai 2017 à 22:30, David Hart a écrit : >> >> Can you explain what’s the problem with Issue 2? > > The problem was me, I guess :-) Of course nobody knows the list of keys, but > the type

Re: [swift-evolution] Feedback on SE-0166 and SE-0167

> Le 26 mai 2017 à 22:30, David Hart a écrit : > > Can you explain what’s the problem with Issue 2? The problem was me, I guess :-) Of course nobody knows the list of keys, but the type itself. It's a matter of injecting an encoder. I'll do that. Thanks also Itai for your