Scala Day Two

The second day of Java for Hipsters Scala looked at the functional side of the language and how we can we can use a robust collection API to write cleaner, more concise code.

  1. Things to find
  2. A discussion on how to use Scala files
  3. What makes a closure different from a code block
  4. Things to do
  5. List comprehension
  6. Traits and maps
  7. Loading Scala from a file
  8. Thoughts

Things to find

A discussion on how to use Scala files

A quick search pulls up this blog post by David Bryant Copeland, and what he has to say about working with files in Scala is anything but reassuring. There are some interesting answers in this Stack Overflow question, and typically there is some discussion around performance when handling large files (as there always is in programmer circles). Daniel Sobral’s answer seems the cleanest syntactically, so it’s the one I’m likely to use.

What makes a closure different from a code block

In Scala, a code block is a function that sequentially evaluates expressions and returns the value of the last expression; nothing strange there. A closure is slightly more interesting because it has at least one indirect dependency. As I understand it, both types of functions can be assigned to variables and passed around as parameters to other functions, just like JavaScript.

Things to do

List comprehension

Use foldLeft to compute the total size of a list of strings.

Scala’s foldLeft is similar to the reduce method from Ruby or Io. It takes a start value, which in our case is 0. We can then perform some function with the accumulator and the current list item. We take the current list item’s string length, add it to the accumulated value, and continue through the list.

Traits and maps

Write a Censor trait with a method that will replace the curse words Shoot and Darn with Pucky and Beans alternatives. Use a map to store the curse words and their alternatives.

Scala uses ‘traits’ to handle multiple inheritance, and I think it’s a neat idea. I haven’t relied upon multiple inheritance in practice, but traits apparently mitigate the “Deadly Diamond of Death” problem. To use it, we need to mix it into a class. Instances of a class that extend a trait can then use properties and methods from that trait.

Loading Scala from a file

Load the curse words and alternatives from a file.

To start working through this problem, I created a CSV file with the curse words and their alternatives. We can open the file with the code we found earlier. Since we’re doing mkString, we have to split on a new line character, which gives us an array of the lines in the file.

We use the map method to perform some action with each item in the array; in this case, we’re splitting on the comma and returning a tuple. Once we have a list of tuples, it’s trivial to convert that to a map.


This second day of Scala study was less daunting than the first. I was expecting to dodge a curve ball with the functional side of Scala, but aside from syntax it’s not too different from Ruby or Io.

What I’ve been noticing is that the somewhat flexible syntax often leads to one-liners, albeit hard-to-read, 100+ character long one-liners. From reading a bunch of Stack Overflow answers, it feels almost idiomatic for Scala to be written as “heiroglyphic syntax soup”, which is either acceptable and takes getting used to, or not acceptable.

I think I’ll try to really make a point of formatting my Scala code neatly. I wouldn’t want to lose any dedicated developers.