Re: [swift-evolution] [Pitch] Changing NSObject dispatch behavior

> On 30 Dec 2016, at 10:50 am, Freak Show wrote: > > >> On Dec 29, 2016, at 13:28, Rod Brown via swift-evolution >> wrote: >> >> I’m in agreement that ‘dynamic’ is probably not what you want without a >> declaration. > > I hold a completely

Re: [swift-evolution] [Pitch] Changing NSObject dispatch behavior

on Thu Dec 29 2016, Freak Show wrote: >> On Dec 29, 2016, at 13:28, Rod Brown via swift-evolution >> wrote: >> >> I’m in agreement that ‘dynamic’ is probably not what you want without a >> declaration. > > I hold a completely opposite

Re: [swift-evolution] [Pitch] Changing NSObject dispatch behavior

> On Dec 29, 2016, at 13:28, Rod Brown via swift-evolution > wrote: > > I’m in agreement that ‘dynamic’ is probably not what you want without a > declaration. I hold a completely opposite viewpoint. Dynamic is always what I want and table based is premature

Re: [swift-evolution] Replace named returns with `out` parameters?

I know you've already decided against this, but I think it deserves an explanation for why the two are different. Tuples in function parameters was basically a special case to the type system. The function type was effectively modeled as taking one argument which was a tuple, and a function of

Re: [swift-evolution] [Pitch] Changing NSObject dispatch behavior

I’m in agreement that ‘dynamic’ is probably not what you want without a declaration. There are currently some bugs in how dispatch works for overrides in Swift extensions, and I’d like to see any methods that conform to an @objc protocol being given an implicit @objc, but true dynamic? No.

Re: [swift-evolution] URL Literals

I think for me, the big difference between a color literal and URL literal, which swayed me in the end was this: As noted in SE-0039, `[#Color(...)#]` (now `#colorLiteral(...)`) isn't itself a literal; it's a spelling that allows you to _get_ a literal, which is a swatch of color. On reflection,

Re: [swift-evolution] URL Literals

On Thu, Dec 29, 2016 at 3:18 PM, Micah Hainline wrote: > I think that's all doable. I'm not sure what delimiters would be the > best though, which is why I hadn't moved away from #url yet. I've been > thinking hard about the regex, which seems like an even stronger case

Re: [swift-evolution] URL Literals

I think that's all doable. I'm not sure what delimiters would be the best though, which is why I hadn't moved away from #url yet. I've been thinking hard about the regex, which seems like an even stronger case to make into a literal, and /abc/ works well for those, but even those have some