Welcome to the Treehouse Community

The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.

iOS Swift 2.0 Functions Functions in Swift 2.0 Return Types

Darius Moravcik
Darius Moravcik
6,879 Points

Compilor error with Swift 3 vs. Swift 2

I'm using Swift 3 and when I wrote our the code for the next code challenge inside the Xcode Playground it was fine, but when I copy-pasted it to Treehouse I was getting a compilor error. I think it's because of the difference in Swift versions used. I just wanted to share the solution in case somebody else was getting the same error and doesn't know where it's coming from.

Here was my code that worked in Swfit 3, but not in Treehouse in the last part of the challenge when calling the function:

let fahrenheitTemp = temperatureInFahrenheit(temperature: 24.0)

Afterwards, I deleted the "temperature" bit and it worked fine, like this:

let fahrenheitTemp = temperatureInFahrenheit(24.0)

Did anybody else have the same experience, or did I miss something?

1 Answer

David Papandrew
David Papandrew
8,386 Points

Hi Darius,

You are correct. Swift 3 requires the first parameter name as well as the value when you call a function. Swift 2 doesn't. With Swift 2, unless you explicitly define an external parameter name for the first parameter in your function, you do not provide use that name when calling the function. So as in your example, you would just pass the value without the parameter name/label.

Will the swift 3.0 update affect all the challenges like this one on the track?