Method overloading in Java - Time & Space Complexity

Time Complexity: Method overloading

O(1)

Understanding Time Complexity

We want to understand how the time it takes to run a program changes when using method overloading.

Specifically, does having multiple methods with the same name but different inputs affect how long the program runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class Calculator {
    public int add(int a, int b) {
        return a + b;
    }

    public int add(int a, int b, int c) {
        return a + b + c;
    }
}
    

This code defines two methods named add but with different numbers of inputs. It shows method overloading.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Simple addition operations inside each method.
• How many times: Each method runs once per call; no loops or recursion.

How Execution Grows With Input

Since each method just adds a fixed number of numbers, the work does not grow with input size.

Input Size (n)	Approx. Operations
10	2 or 3 additions (max)
100	2 or 3 additions (max)
1000	2 or 3 additions (max)

Pattern observation: The number of operations stays the same no matter how big the input numbers are.

Final Time Complexity

Time Complexity: O(1)

This means the time to run these methods stays constant regardless of input size.

Common Mistake

[X] Wrong: "Having multiple methods with the same name makes the program slower because it has to check all of them."

[OK] Correct: The program chooses the right method to run before it starts, so it does not waste time checking at runtime.

Interview Connect

Understanding method overloading helps you write clear code and shows you know how programs pick the right method quickly.

Self-Check

"What if one of the overloaded methods used a loop to add numbers? How would the time complexity change?"

Practice

1.

What is method overloading in Java?

easy

A. Changing the return type of a method only

B. Having multiple classes with the same name

C. Using inheritance to override methods

D. Having multiple methods with the same name but different parameters

Solution

1. Step 1: Understand method naming

   Method overloading means methods share the same name.

2. Step 2: Check parameter differences

   They differ by number or type of parameters, not just return type.

3. Final Answer:

   Having multiple methods with the same name but different parameters -> Option D

4. Quick Check:

   Same name + different parameters = method overloading [OK]

Hint: Same method name, different parameters means overloading [OK]

Common Mistakes:

• Confusing overloading with overriding
• Thinking return type alone overloads method
• Mixing class names with method names

2.

Which of the following is a correct method overloading example in Java?

class Test {
  void show(int a) {}
  void show(int a, int b) {}
  void show(int a) {}
}

easy

A. This code compiles without errors

B. Duplicate method show(int a) causes a compile error

C. Method names must be different to overload

D. Return types must differ for overloading

Solution

1. Step 1: Check method signatures

   Two methods have the same name and same parameter list: show(int a).

2. Step 2: Understand overloading rules

   Overloading requires different parameter lists; duplicate signatures cause errors.

3. Final Answer:

   Duplicate method show(int a) causes a compile error -> Option B

4. Quick Check:

   Same parameters = error, not overloading [OK]

Hint: Parameters must differ; identical signatures cause errors [OK]

Common Mistakes:

• Assuming return type difference overloads method
• Ignoring duplicate parameter lists
• Thinking method names must differ

3.

What is the output of this Java code?

class Demo {
  void print(int a) {
    System.out.println("int: " + a);
  }
  void print(String s) {
    System.out.println("String: " + s);
  }
}
public class Main {
  public static void main(String[] args) {
    Demo d = new Demo();
    d.print(5);
    d.print("hello");
  }
}

medium

A. int: 5\nString: hello

B. String: 5\nint: hello

C. int: 5\nint: hello

D. Compilation error

Solution

1. Step 1: Identify method calls and parameters

   First call passes int 5, second call passes String "hello".

2. Step 2: Match calls to overloaded methods

   print(int) prints "int: 5", print(String) prints "String: hello".

3. Final Answer:

   int: 5 String: hello -> Option A

4. Quick Check:

   Correct method chosen by parameter type [OK]

Hint: Method chosen by argument type matches parameter [OK]

Common Mistakes:

• Mixing output order
• Assuming wrong method called
• Expecting compile error

4.

Find the error in this code snippet:

class Calculator {
  int add(int a, int b) { return a + b; }
  double add(double a, double b) { return a + b; }
  int add(int a, int b, int c) { return a + b + c; }
  int add(int a, int b) { return a - b; }
}

medium

A. Duplicate method add(int a, int b) with different body causes error

B. Overloading requires different method names

C. Return type difference causes error

D. No error, code compiles fine

Solution

1. Step 1: Check method signatures

   Two methods have signature add(int a, int b) but different bodies.

2. Step 2: Understand overloading rules

   Overloading requires unique parameter lists; duplicate signatures cause errors regardless of body.

3. Final Answer:

   Duplicate method add(int a, int b) with different body causes error -> Option A

4. Quick Check:

   Same parameters = duplicate method error [OK]

Hint: Same parameters, different body = error, not overloading [OK]

Common Mistakes:

• Thinking different return types fix duplicates
• Ignoring duplicate parameter lists
• Confusing overloading with overriding

5.

Consider this class:

class Converter {
  int convert(String s) { return Integer.parseInt(s); }
  int convert(int i) { return i * 2; }
  int convert(String s, int base) { return Integer.parseInt(s, base); }
}
public class Main {
  public static void main(String[] args) {
    Converter c = new Converter();
    System.out.println(c.convert("10"));
    System.out.println(c.convert(10));
    System.out.println(c.convert("10", 16));
  }
}

What is the output when this code runs?

hard

A. Runtime error parsing string

B. 10\n20\n10

C. 10\n20\n16

D. Compilation error due to ambiguous methods

Solution

1. Step 1: Analyze each method call

   convert("10") parses string "10" as decimal 10; convert(10) doubles 10 to 20; convert("10", 16) parses hex "10" as decimal 16.

2. Step 2: Determine output values

   Outputs are 10, 20, and 16 respectively.

3. Final Answer:

   10 20 16 -> Option C

4. Quick Check:

   Overloaded methods handle inputs correctly [OK]

Hint: Match method by parameters; parseInt with base converts hex [OK]

Common Mistakes:

• Confusing hex parsing result
• Expecting compile or runtime errors
• Mixing method outputs