Re: [swift-evolution] SE-0025: Scoped Access Level, next steps

> On Mar 14, 2016, at 7:38 PM, Sean Heber via swift-evolution > wrote: > > I, too, prefer it to be more like this: > > public // unchanged > module // currently internal > internal // currently private > private // new hotness I like these best out of what’s been suggested so far. I agree

Re: [swift-evolution] [SE-0011] Re-considering the replacement keyword for "typealias"

How about 'deferred’? As in one of the following: typealias MyType = deferred or: deferredtype MyType or: deferred typealias MyType (apologies if this was already suggested previously) > On Dec 22, 2015, at 9:30 AM, Erica Sadun via swift-evolution > wrote: > > As SE-0011 states, the concept

Re: [swift-evolution] Swift case conventions for Enums

> On Dec 21, 2015, at 3:58 PM, Michael Wells via swift-evolution > wrote: > > I love that Swift has a published API design guidelines at > https://swift.org/documentation/api-design-guidelines.html > , but one thing > about it bugs

Re: [swift-evolution] Proposal: Remove % operator for floating-point types

> > I don't think this solves the precision issue. It makes it harder to use > fmod, but doesn't stop people wanting to, life finds a way. I completely > agree with your rationale, but if someone wants mod they'll use mod. The > question probably comes down to whether stackoverflow will tell th