Practical difference between def f(x: Int) = x+1 and val f = (x: Int) => x+1 in Scala

后端 未结 2 1720
清酒与你
清酒与你 2021-02-20 14:19

I\'m new to Scala and I\'m having a problem understanding this. Why are there two syntaxes for the same concept, and none of them more efficient or shorter at that (merely from

相关标签:
2条回答
  • 2021-02-20 14:39

    There are three main differences (that I know of):

    1. Internal Representation

    Function expressions (aka anonymous functions or lambdas) are represented in the generated bytecode as instances of any of the Function traits. This means that function expressions are also objects. Method definitions, on the other hand, are first class citizens on the JVM and have a special bytecode representation. How this impacts performance is hard to tell without profiling.

    2. Reference Syntax

    References to functions and methods have different syntaxes. You can't just say foo when you want to send the reference of a method as an argument to some other part of your code. You'll have to say foo _. With functions you can just say foo and things will work as intended. The syntax foo _ is effectively wrapping the call to foo inside an anonymous function.

    3. Generics Support

    Methods support type parametrization, functions do not. For example, there's no way to express the following using a function value:

    def identity[A](a: A): A = a
    

    The closest would be this, but it loses the type information:

    val identity = (a: Any) => a
    
    0 讨论(0)
  • 2021-02-20 14:39

    As an extension to Ionut's first point, it may be worth taking a quick look at http://www.scala-lang.org/api/current/#scala.Function1.

    From my understanding, an instance of a function as you described (ie. val f = (x: Int) => x + 1) extends the Function1 class. The implications of this are that an instance of a function consumes more memory than defining a method. Methods are innate to the JVM, hence they can be determined at compile time. The obvious cost of a Function is its memory consumption, but with it come added benefits such as composition with other Function objects.

    If I understand correctly, the reason defs and lambdas can work together is because the Function class has a self-type (T1) ⇒ R which is implied by its apply() method https://github.com/scala/scala/blob/v2.11.8/src/library/scala/Function1.scala#L36. (At least I THINK that's what going on, please correct me if I'm wrong). This is all just my own speculation, however. There's certain to be some extra compiler magic taking place underneath to allow method and function interoperability.

    0 讨论(0)
提交回复
热议问题