Scala: An attempt to eradicate the if
In a previous post I included a code sample where we were formatting a page range differently depending on whether the start page and end pages were the same.
The code looked like this:
trait PageAware {
def startPage:String
def endPage:String
def pageRange = if(firstPage == lastPage) "page %s".format(firstPage) else "pages %s-%s".format(firstPage, lastPage)
}
Looking at the if statement on the last line we were curious whether it would be possible to get rid of it and replace it with something else.
In Java we could use the ternary operator:
public class PageAware {
public String pageRange() {
return (firstPage == lastPage) ? String.format("page %s", firstPage) : String.format("pages %s-%s", firstPage, lastPage)
}
}
The if/else statement in Scala is supposed to replace that as far as I understand but I think the ternary operator looks neater.
Beyond defining that we played around with some potential alternatives.
We could use a Map to store the true and false values as keys:
trait PageAware {
def pageRange = Map(true -> "page %s", false -> "pages %s-%s")(firstPage == lastPage).format(firstPage, lastPage)
}
Uday came up with a pattern matching solution which looks like this:
trait PageAware {
def pageRange = ((firstPage, lastPage) match { case (`firstPage`, `firstPage`) => "page %s" case _ => "pages %s-%s"}).format(firstPage, lastPage)
}
Unfortunately both of these solutions are significantly less readable than the if/else one so it seems like this is one of the situations where it doesn’t actually make sense to get rid of it.
About the author
I'm currently working on short form content at ClickHouse. I publish short 5 minute videos showing how to solve data problems on YouTube @LearnDataWithMark. I previously worked on graph analytics at Neo4j, where I also co-authored the O'Reilly Graph Algorithms Book with Amy Hodler.