One example is matching you can see several uses of matching in the following topics:
But matching it applies to today's topic as well. This topic covers a cool trick that helps assist with parameter objects and complex return types.
This topic is another take on Assignment and Parameter Objects. There are cases when a method has a large number of parameters and the API can be cleaned up by introducing a parameter object. Or perhaps an object with several public proprties are passed to a method.
- scala> case class Params(p1:Int, p2:Int, p3:Int)
- defined class Params
- scala> def method(params:Params) = {
- | println(params.p1, params.p2, params.p3)
- | }
- method: (Params)Unit
- scala> method(Params(1,2,3))
- (1,2,3)
- }
The symbol 'params' introduces noise into the code. The noise can be reduced further by assigned the properties of the parameter object to local variables:
- scala> case class Params(p1:Int, p2:Int, p3:Int)
- defined class Params
- scala>
- scala> def method(params:Params) = {
- | val Params(p1,p2,p3) = params
- | println(p1,p2,p3)
- | }
- method: (Params)Unit
- scala> method(Params(1,2,3))
- (1,2,3)
- }
But we can do better remember that we can import methods and properties from an object:
- scala> object Obj {
- | val prop = 10
- | }
- defined module Obj
- scala> import Obj._
- import Obj._
- scala> println(prop)
- 10
Since all instance are objects it is possible to import fields and methods from instances as well:
- scala> case class Params(p1:Int, p2:Int, p3:Int)
- defined class Params
- scala>
- scala> def method(params:Params) = {
- | import params._
- | println(p1, p2, p3)
- | }
- method: (Params)Unit
- }
The same technique is extremely useful when a method needs to return multiple values:
- scala> def method() = {
- | (1,2,3)
- | }
- method: ()(Int, Int, Int)
- scala> val retVal = method()
- retVal: (Int, Int, Int) = (1,2,3)
- /*
- retVal is a tuple so we can import the tuple
- properties. Becareful to not do this multiple times in
- the same scope
- */
- scala> import retVal._
- import retVal._
- scala> println(_1,_2,_3)
- (1,2,3)
- scala> def method2={
- // Notice case class declaration can be contained in method
- | case class Return(v1:Int,v2:Int)
- | Return(6,7)
- | }
- method2: java.lang.Object with ScalaObject with Product{def v1: Int; def v2: Int}
- scala> val r = method2
- r: java.lang.Object with ScalaObject with Product{def v1: Int; def v2: Int} = Return(6,7)
- scala> import r._
- import r._
- scala> println(v1,v2)
- (6,7)
- }
Thanks for another very informative and useful post. I love these daily tips.
ReplyDeleteOne question, in the last example method2 defines a case class called "Return" but the type shown in the interactive output is called "Product". Is this just an editing error or am I missing something?
Hi, I didn't notice that. Good observation!
ReplyDeleteThe method 'method2' does in fact return a Product that is not an error. If you look at the signature it is:
java.lang.Object with ScalaObject with Product{def v1: Int; def v2: Int} = Return(6,7)
So it is a Product{def v1: Int; def v2: Int} which declares that it has the methods v1 and v2. So when importing that object it will import v1 and v2 into the current scope.
The type of the val cannot be Return because it is not in scope. So the compiler automatically infers Product{def v1: Int; def v2: Int} which all case classes are automatically.
I will make a post about Products and mention the relation to case classes.