Re: [swift-users] A confusing protocol extension behaviour/bug

Rest of message - hit send by mistake. The problem is that it is really easy to make the mistake you made. There have been a number of suggestions on Swift Evolution to add key words so that diagnostics can be improved. For example: protocol P { func m() } extension P {

Re: [swift-users] A confusing protocol extension behaviour/bug

Unfortunately the error messages you get with protocols are limited :). The compiler is doing the right thing, no bug. The problem is that it is really easy to mak -- Howard. > On 1 Jan 2018, at 3:40 pm, Toni Suter via swift-users > wrote: > > Hi Marc, > > There are

Re: [swift-users] Rethrows issue

I don’t get why that type checks: 1. rescue always throws inside sync, therefore 2. _syncHelper inside sync always throws, therefore 3. sync always throws, therefore 4. Shouldn’t sync be declared throws not rethrows? -- Howard. On 1 Jan 2018, at 1:10 pm, Charles Srstka via swift-users

Re: [swift-users] Happy new year Swift community.

Happy new year! Greetings from Cyprus :) George. > On 1 Jan 2018, at 1:42 AM, Adrian Zubarev via swift-users > wrote: > > Well some of you guys have to wait a little longer, but I can already wish > everyone a happy new year from Germany.  > > -- > Adrian

Re: [swift-users] Happy new year Swift community.

Happy new year from klossyland! On Mon, Jan 1, 2018 at 11:23 AM, Georgios Moschovitis via swift-users < swift-users@swift.org> wrote: > Happy new year! Greetings from Cyprus :) > > George. > > On 1 Jan 2018, at 1:42 AM, Adrian Zubarev via swift-users < > swift-users@swift.org> wrote: > > Well

Re: [swift-users] Happy new year Swift community.

Happy New Year from Canada ! On Jan 1, 2018, at 14:02, Kelvin Ma via swift-users > wrote: Happy new year from klossyland! On Mon, Jan 1, 2018 at 11:23 AM, Georgios Moschovitis via swift-users

Re: [swift-users] A confusing protocol extension behaviour/bug

Hi Marc, There are several subtleties here, but I think the compiler is actually doing the right thing. The second class defines a static property that looks like it is 'overriding' the static property from the protocol extension, but since the types don't match (String vs. String?), it sort

Re: [swift-users] Rethrows issue

> On Dec 31, 2017, at 1:35 AM, Nevin Brackett-Rozinsky via swift-users > wrote: > > So, I know this doesn’t actually address your issue, but I think it is > important to clarify that “rethrows” does not guarantee anything about the > *type* of error thrown by a

Re: [swift-users] [swift-evolution] Happy new year Swift community.

Happy New Year! > On Dec 31, 2017, at 6:01 PM, Goffredo Marocchi via swift-evolution > wrote: > > Happy new year everybody :)! > > Sent from my iPhone > > On 31 Dec 2017, at 23:43, David Hart via swift-evolution >

[swift-users] A confusing protocol extension behaviour/bug

Hi, I hope everybody had a great New Year celebration. I was tracking down a weird bug in my Swift code today. A property defined in a class in order to conform to a protocol was not being seen. A protocol extension provided a default value of `nil` for this property, so I knew where it was