On Mon, Apr 4, 2016 at 7:25 AM, Jim Malak via swift-users <
swift-users@swift.org> wrote:
> what purpose does requiring the keyword “func” serve when defining or
> decaling a function in Swift.
>
func someFunction() {
}
someFunctionThatTakesAClosure() {
}
-david
_
Thanks. I’ve got it now.
I reported several suggestions for the Getting Started and Download
instructions.
Dave
> On 2016-04-03, at 7:37 PM, Daniel Dunbar wrote:
>
> If you build swift yourself you need to point directly at swift-build. Most
> people grab the pre-built toolchains from swift.
Thanks Jens,
My main languages are C#, c, obj-c and now Swift. You can appreciate my point
of view. I’ll just assume that adding “func” contributes towards the common
good.
Thanks for responding.
- Jim
From: Jens Alfke
Date: Monday, April 4, 2016 at 2:32 PM
To: Jim Malak
Cc: "swif
> On Apr 4, 2016, at 7:25 AM, Jim Malak via swift-users
> wrote:
>
> My background going into Swift was everything but JavaScript.
Have you used Ruby or Python, both of which use a “def” keyword before a
definition? And come to think of it, I think most non-C-derived languages use
some sort
I'm working on a project using Swift 2.1. I upgraded my Xcode to the latest
and now see hundreds of warnings for Swift 2.2 improvements (mostly things
like the change in selector syntax). Is there a way to turn off Swift 2.2
warnings in favor of Swift 2.1 warnings in Xcode?
I can't go in an fix
My background going into Swift was everything but JavaScript. One thing I often
wondered about (usually every time I forgot to type it) is what purpose does
requiring the keyword “func” serve when defining or decaling a function in
Swift. I am not a compiler expert but intuitively it would seem
