underscoreio / eescala Goto Github PK

The principle of using types as constraints is good, but Calculation is a huge exercise for such a short course.

Possibly replace it by implementing an itemAt method on IntList, identifying the NullPointerException, and then resolving it with an Option-like type:

trait IntList {
  def itemAt(index: Int): ???
}

The andThen example in the code is a little complex -- people tend to have difficulty with the syntax for the later examples.

Probably need to add an example with simpler syntax, e.g. a method that accepts a function and returns something other than a function.

There are two ways of implementing pattern matching solutions to many of the exercises in the slides:

1. Put the match expression in a method in a companion object;
2. Put the match expression in the super-trait.

We should have an explicit example of each before we start using them in solutions.

There's a lot of syntax to take in over the duration of the course, and not enough time to properly reinforce it. A crib sheet may help alleviate this problem.

The start is confusing and time consuming for such a short course. This order may work better:

• introduce classes first, before objects:
  • provide a complete example with field definitions;
  • exercise 1 is cats as regular classes;
• introduce case classes next:
  • exercise 2 is cats as regular classes;
• introduce objects third:
  • possibly no example;
• skip the bit about "classes abstract over objects" (perhaps mention in the part 1 summary);

The syntax doesn't make it clear where the match happens. Put the code example in the slide in a method.