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 Build an Interactive Story App with Swift Creating a Story Helper Methods

Christopher Debove
PLUS
Christopher Debove
Courses Plus Student 18,371 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

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.