Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Marcos Reboucas
12,890 PointsCould anyone tell me what's wrong with this closure syntax?
I'm getting: Make sure the method is named fetchTreehouseBlogPosts and has the correct syntax!
Also the preview:
swift_lint.swift:7:45: error: expected ',' separator typealias BlogPostCompletion = (data:NSData!;
response:NSURLResponse!; error:NSError!) -> Void ^ , swift_lint.swift:7:45: error: expected type typealias
BlogPostCompletion = (data:NSData!; response:NSURLResponse!; error:NSError!) -> Void ^ swift_lint.swift:7:45: error:
expected ',' separator typealias BlogPostCompletion = (data:NSData!; response:NSURLResponse!; error:NSError!) -> Void
^ ,
import Foundation
// Add your code below
typealias BlogPostCompletion = (data:NSData!, response:NSURLResponse!, error:NSError!) -> Void
func fetchTreehouseBlogPosts (completion: BlogPostCompletion)
{
}
2 Answers
Roberta Voulon
5,792 PointsWhat made it work for me in the end was wrap the signature in outer parenthesis like this:
typealias BlogPostCompletion = ((NSData!, NSURLResponse!, NSError!) -> Void)
func fetchTreehouseBlogPosts(completion: BlogPostCompletion) {}
It's really silly, I was stuck on this for days, I didn't even know this is correct syntax, and they're not necessary!
Trevor Moore
5,207 PointsYep I was totally stuck on this, I thought I was misunderstanding the question. Very frustrating!