Method Invocation is a technique which demonstrate different synatx in which we dynamically call methods of a class with an object.
The naming conventions of Scala are same as of Java, that are:-
- There should not be any space between the invocation object/target and the dot(.) nor a space between the dot and method name.
obj.display(“name”) // correct
obj.display (“name”) // incorrect but legal
obj. display(“name”) // incorrect but legal
- Nor there should not be any space between the method name and the parantheses.
println(“student”) // correct
println (“student”) // incorrect but legal
- The arguments should be seperated by a single space and a comma.
obj.display(“name”, 22) // correct
obj.display (“name”, 22) // incorrect but legal
obj. display(“name”, 22) // incorrect but legal
Let’s see methods with different arguments and styles.
Arity-0 : When there are 0 arguments to be passed to the method. Hence it is not mandatory to add parenthesis on methods. It will enhance the readability of the code and omission of parenthesis will reduce the number of characters to some extent.
obj.display() //correct obj.display //correct
Arity-1 : When there is only 1 argument to be passed to the method of arity-1. This rule should be used for purely-functional programming or the methods that take functions as parameters, then it is parenthesis can be avoided around the passed parameter. This type of syntax is also known as infix notation.
student student student
Higher order function : A function is called Higher Order Function if it contains other functions as a parameter or returns a function as an output i.e, the functions that operate with another functions are known as Higher order Functions. It is worth knowing that higher order function is applicable for functions and methods as well that takes functions as parameter or returns a function as a result. This is practicable as the compiler of Scala allows to force methods into functions.
Multiplied List is: Set(captain sunil, captain akhil, captain rakhi)
- These syntax should be followed when there are no side-effects.
- These conventions are used to improve the readability and make the code much easier to understand.
- It can save some space by neglecting some extra characters.
- Scala Map get() method with example
- Scala | map() method
- Scala map contains() method with example
- Scala Map max() method with example
- Scala Map min() method with example
- Scala Map last() method with example
- Scala Map take() method with example
- Scala List map() method with example
- Scala Map remove() method with example
- Scala Iterator max() method with example
- Scala | unapplySeq() method
- Scala Map keys() method with example
- Scala Iterator min() method with example
- Scala Map size() method with example
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.