I have a simple question along this line: How does expanding the capabilities
of Swift detract or impair its use in a fully OO manner? From what I have seen,
if you want to use it in a strictly OO manner, great! If you want to use it in
a strictly functional manner, no problem. If you want to us
), it was not removed.
>
> I recommend filing a bug report at bugreport.apple.com
> <http://bugreport.apple.com/>
>
> -- E
>
>
>> On Sep 8, 2016, at 3:23 PM, Michael Sheaver via swift-users
>> mailto:swift-users@swift.org>> wrote:
>>
>> This is jus
This is just a heads-up for all who might be using/enjoying/playing with Swift
Playgrounds on the iPad; it has apparently been removed from the GM that was
released yesterday. There are a couple posts about it in the Apple forums, but
no definitive answers have been posted as yet. I searched in
our specific case,
>
> let calendar2 = (currentLocale as
> NSLocale).object(forKey:NSLocale.Key(rawValue:propertyName))
>
> is just almost the same as `let calendar2 = calendar1`.
>
> If you insist on using `NSLocale.Key`, you should use `NSLocale` instead of
> `Locale`.
&g
I am trying to build a table of current locale properties in code, and have
encountered issues with trying to pass the value of a variable to a function:
let currentLocale = Locale(identifier: "en_US")
let calendar1 = currentLocale.calendar // "gregorian (fixed)"
let propertyName = "calend
I am attending WWDC and would love to attend this proposed meetup - if you all
can tolerate a Swift baby who is just learning to crawl! :)
Sent from my iPhone
On Jun 6, 2016, at 7:08 AM, Michael Nisi via swift-users
wrote:
Great initiative—and a really interesting question: how many Swift Ope
