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

iOS Build an Interactive Story App with Swift Creating a Story Helper Methods

Christopher Debove
PLUS
Christopher Debove
Courses Plus Student 18,373 Points
Posted by Christopher Debove
Christopher Debove
Courses Plus Student 18,373 Points

Why do not use wildcard pattern matching in addChoiceWith

In the extension function addChoiceWith, here is what Pasan propose:

  switch (firstChoice, secondChoice) {
    case (.some, .some): return self
    case (.none, .none), (.none, .some): firstChoice = (title, page)
    case (.some, .none): secondChoice = (title, page)
  }

Why not use this ?

  switch (firstChoice, secondChoice) {
    case (.some, .some): return self
    case (.none, _): firstChoice = (title, page)
    case (.some, .none): secondChoice = (title, page)
  }

1 Answer

Clark Reilly
Clark Reilly
6,204 Points
Clark Reilly
Clark Reilly
6,204 Points

Both work. Do whatever, I guess. Pasan probably didn't use it because he hasn't explained what wildcard pattern matching is yet, so nobody would know what he was talking about at this point.