Lambdas are just anonymous functions, although typically they are expected to be side-effect free (more of a calculus-style function that does a computation)<\/p>\n
For instance, in Javascript you might do this:<\/p>\n
\nfunction x() {\n}\n\n...or....\n\nvar y = function() { }\n\n<\/pre>\nThe equivalent in Scala might be:<\/p>\n
\nval y = () => {}\n<\/pre>\n \ny()\ny: () => Unit = \n<\/pre>\nSo you can see the type it returns is “Unit” which appears approximately equivalent to “void”, however unlike “void” in Java you can declare things as Unit (although with only a single value):<\/p>\n
\nval x: Unit = ()\n<\/pre>\nWhether this is useful is questionable.<\/p>\n
You could, for instance make a lambda that doubles a value, and use it like so (the forms listed are all equivalent):<\/p>\n
\nval y = (x: Int) => x * 2\n\nList(1, 2, 3).map(y)\nList(1, 2, 3) map y\nList(1, 2, 3).map((x: Int) => x * 2)\n<\/pre>\nAll returning:<\/p>\n
\nres11: List[Int] = List(2, 4, 6)\n<\/pre>\nThere isn’t a way to make the lambda type-less (or generic):<\/p>\n
\nval y = (x) => x\n\n:8: error: missing parameter type\n val y = (x) => x\n<\/pre>\nThat said, you can cheat this a couple ways, either with Any (most similar to void* in C):<\/p>\n
\nval y = (x: Any) => x\n\ny: Any => Any = \n<\/pre>\nOr, instead of making a lambda, make a method (T being a generic type here):<\/p>\n
\ndef y[T] = (x: T) => x \n<\/pre>\nWhich does actually work:<\/p>\n
\ny: [T]=> T => T\n\nscala> y(1)\nres7: Int = 1\n<\/pre>\nThis is basically defining a method in some object (less obvious if you’re typing the Scala REPL), although it might otherwise behave similarly to lamdbas. This is familiar, in that it is similar to methods in Java.<\/p>\n
In the shorter lambdas, the lack of a “return” feels very natural, but as these get longer it starts to feel weird. This is especially true if the code gets longer – when there are multiple statements, the result of the last one is implicitly returned (when writing code, it can be helpful to define the return type of the function, so you get an error if you accidentally return the wrong thing)<\/p>\n
You should resist the temptation to add “return” to your functions. The authors of Scala made the questionable decision to change the traditional meaning of return, such that it takes you out of all lambdas, and up out of the most recent method on the stack – which is likely quite a ways up, and not at all what you’d expect.<\/p>\n","protected":false},"excerpt":{"rendered":"
Lambdas are just anonymous functions, although typically they are expected to be side-effect free (more of a calculus-style function that does a computation) For instance, in Javascript you might do this: function x() { } …or…. var y = function() { } The equivalent in Scala might be: val y = () => {} y() … <\/p>\n