{{announcement.body}}
{{announcement.title}}

7 Uses of Underscore in Scala

DZone 's Guide to

7 Uses of Underscore in Scala

Underscores are overloaded in Scala: see 7 places where '_' means different things.

· Java Zone ·
Free Resource

This article is for the curious Scala programmer who has seen underscores more times than they'd find comfortable. In this article I'll share almost all the places where you might see an underscore, so that you don't freak out when you see yet another one in a different context.

You can also read this article over at the Rock the JVM blog or watch the video version of it on YouTube or embedded below:


Other than that, I want to get straight to the point.

1. Ignoring

Underscores are commonly used when names or values are not important and/or unused. Here is a comprehensive list of ignored elements. First, variable names:

Scala
 




x


1
val _ = 5



Why you'd do that, I have no idea - the point of intentionally declaring a value or variable is to use it. But it's possible. Probably the most useless case of an underscore. However, the case when the compiler throws a value at use, but we don't use it, so we use an underscore. The most common use case is with lambdas whose arguments we don't need or use:

Scala
 




xxxxxxxxxx
1


1
val onlyFives = (1 to 10).map(_ => 5)



We could have said (1 to 10).map(x => 5) but we don't need x and the compiler would have issued an unused variable warning anyway, so we replace with an underscore.

Another scenario is when we use self-types as a type restriction, but you don't actually need to name the self-type:

Scala
 




xxxxxxxxxx
1


 
1
trait Singer
2
trait Actor { _: Singer =>
3
  // implementation
4
}



Finally, one of the less common places where underscores ignore stuff is generic types. For example:

Scala
 




xxxxxxxxxx
1


1
def processList(list: List[Option[_]]): Int =  list.length



Since we don't care what type those Options are, we type them with underscore. Underscores are also useful when we want to interoperate with Java libraries or generic types which were not explicitly typed (think pre-Java 5).

2. Wildcards

Underscores are also used to have the meaning of "everything" in certain contexts. One of them is importing everything in a package:

Scala
 







But by far the most frequent use case is in pattern matching, where the underscore means "match everything".

Scala
 




xxxxxxxxxx
1


 
1
meaningOfLife match {
2
  case _ => "I'm fine with anything"
3
}



3. Default Initializers

Particularly for variables, when we don't know what to initialize them with, let the JVM decide - zero for numerical values, false for Booleans, null for reference types:

Scala
 




xxxxxxxxxx
1


1
var myVariable: String = _



4. Lambda Sugars

You've probably seen this before. Let's say we want to multiply every element of a list by 5, we would do

Scala
 




xxxxxxxxxx
1


1
List(1,2,3,4).map(x => x * 5)



Except there's an even shorter version. We can wrote

Scala
 




xxxxxxxxxx
1


1
List(1,2,3,4).map(_ * 5)



which means the same thing: the compiler expands that to the slightly longer lambda version. The downside is that we can only use the underscore once in the function body - that's because each underscore represents a different argument of the lambda. For example, if I wrote

Scala
 




xxxxxxxxxx
1


1
val sumFunction: (Int, Int) => Int = _ + _



The _ + _ part is identical to (a, b) => a + b. Java programmers seeing this for the first time might find it too short, but it's really easy to get used to it.

5. Eta-expansion

Underscores are also used to turn methods into function values. We talk about the process in detail in another article (check the link above).

Scala
 




xxxxxxxxxx
1


1
def incrementer(x: Int) = x + 1
2
val incrementerFunction = incrementer _



The underscore is a signal to the compiler to create a new lambda with the implementation of x => incrementer(x).

6. Higher-Kinded Types

HKTs are generic types, whose type arguments are themselves generic. Libraries like Cats exploit this like crazy. Their structure is of the form

Scala
 




xxxxxxxxxx
1


1
class MyHigherKindedJewel[M[_]]



Where the type argument M is also generic. If I want to instantiate my HKT with a concrete generic type like List, I'll use the List type (not a List[String] or something else):

Scala
 




xxxxxxxxxx
1


1
val myJewel = new MyHigherKindedJewel[List]



7. Vararg methods

When we have a method taking a variable number of arguments, such as

Scala
 




xxxxxxxxxx
1


1
def makeSentence(words: String*) = ...



we might find ourselves we need to expand some collection of Strings as arguments to this method. We can't pass them manually at runtime, so we need to expand the collection automatically:

Scala
 




xxxxxxxxxx
1


1
val words = List("I", "love", "Scala")
2
val love = makeSentence(words: _*)



In this way, the elements of the list are exploded into the argument list to the method.

Conclusion

Scala overloaded the meaning of the underscore in many, many places - hopefully this article served as a good overview of where you might see it in real code.

Let me know if I've missed anything!

In the meantime, follow Rock the JVM on Twitter, LinkedIn and on the YouTube channel, and check out the Rock the JVM blog for more articles like this!

Topics:
scala

Published at DZone with permission of Daniel Ciocirlan . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}