Re: [swift-users] Amusing function return warning in swift 3

2016-06-12 Thread Nathan de Vries via swift-users
I had similar issues with UIApplicationMain when I moved to Swift 3: UIApplicationMain's argv parameter should be declared nullable Presumably NSApplicationMain's argv parameter needs the same nullable annotation. —Nathan > On Jun 12, 2016, at 3:56 PM, Marco S Hyman via swift-users > wrot

[swift-users] Amusing function return warning in swift 3

2016-06-12 Thread Marco S Hyman via swift-users
My first try with 5/31 swift 3 snapshot gave me a warning regarding an unused return value -- in main.swift. Wouldn’t you know, NS ApplicationMain is declared as func NSApplicationMain(_ argc: Int32, _ argv: UnsafeMutablePointer?>) -> Int32 And what does the second line of function help s

Re: [swift-users] inout params seem to have undefined behavior

2016-06-12 Thread Brent Royal-Gordon via swift-users
> Wow there are some real doozy inout code examples in there, showing > aliasing much more fun than my snippet. Unfortunately I can't > understand anything else the doc is talking about. I guess I'll just > say a prayer and throw salt over my shoulder if using inout. Sorry! Here's the money quot

Re: [swift-users] inout params seem to have undefined behavior

2016-06-12 Thread David Sweeris via swift-users
Oh, ok, I stand corrected. Thanks for the link :-) Sent from my iPhone On Jun 11, 2016, at 18:05, Brent Royal-Gordon wrote: >> My recollection is that in Swift the subscript operator (`arr[2]` in this >> case) can refer to the setter xor the getter, but not both within the same >> statement.