FAQ: Closures - Passing a closure to a function

[discourse-admin]

This community-built FAQ covers the “Passing a closure to a function” exercise from the lesson “Closures”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Learn Intermediate Swift

FAQs on the exercise Passing a closure to a function

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply () below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply () below!
You can also find further discussion and get answers to your questions over in Language Help.

Agree with a comment or answer? Like () to up-vote the contribution!

Need broader help or resources? Head to Language Help and Tips and Resources. If you are wanting feedback or inspiration for a project, check out Projects.

Looking for motivation to keep learning? Join our wider discussions in Community

Learn more about how to use this guide.

Found a bug? Report it online, or post in Bug Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

[mikkohaatainen058093]

This is another of those “guess the exact wording in the suggested solution”. There’s no point to these kinds of overly strict checks.

This does not let me continue to the next task:

let allCards: (Int) → Int = { card in
return card
}

Because this is the only accepted solution:

let allCards = { (card: Int) → Int in
return card
}

[gabriel600]

Step one says there is an Int named “value” but when checking the solution there is nothing named “value”.

Also, this part of the handValue func is confusing (Int) → Int) → Int. I thought the second to last Int should have been the last one. Haaalp.

[kittyamrita1]

Just want to add myself to the list of people who find the wording in this exercise misleading and confusing

[srome11]

Yes. This is ANNOYING

[text9303242957]

I just spent an annoying amount of time trying to find why it was erroring out. It was because it wanted me to call onlyEvens. However, since I typed it out I spelled it correctly and it failed. Fix your stuff!

[land-of-auks]

I could easily be missing something, but I noticed that the opening of this page says “Now that we’ve looked at assigning them (closures) to variables,” but I don’t remember this happening. We assigned them names as constants, but is there a lesson on assigning closures to variables that I’m missing?

[giga1560179418]

this exercise is useless, I spent so much time thinking I’m doing something wrong, while this exercise is just bugged. My recommendation for anyone having issues with this exercise, is to copy the solution and just read the code, dont try to do it yourself, save your time.

[mamacitaboricua]

A year later and add me to that list too. This is utterly confusing. The module says one thing, and then the exercise says another. Completely annoying and honestly this is not the time to make things more confusing but clearer and with similar examples.

[kalabrudzinski]

Glad to see I’m not the only one having issue with this. This whole exercise is just… Doomed. It’s confusing, annoying and stressful. Every time I click on “View Solution” the site just crashes. Cleared cache, tried different browsers and the same happens…

Can you please fix this? This isn’t the quality people pay for!

[mamacitaboricua]

Interesting the site crashed for me too when I was trying to see the solution. I’m just going to learn it and I hope I grasp the concept and then move on!