Dynamic typing vs strong typing in Ruby - Performance Comparison

Time Complexity: Dynamic typing vs strong typing

O(1)

Understanding Time Complexity

When we talk about dynamic typing and strong typing in Ruby, we want to understand how these features affect the speed of running programs.

Specifically, we ask: How does Ruby's way of handling types impact the time it takes to run code?

Scenario Under Consideration

Analyze the time complexity of the following Ruby code that uses dynamic and strong typing.

    def add_values(a, b)
      if a.is_a?(Integer) && b.is_a?(Integer)
        a + b
      else
        "Cannot add non-integers"
      end
    end

    result = add_values(5, 10)
    puts result
    

This code checks the types of inputs at runtime and adds them if both are integers.

Identify Repeating Operations

Look for operations that repeat or take time as input grows.

• Primary operation: Type checking with is_a? method calls.
• How many times: Twice per function call, once for each input.

How Execution Grows With Input

The time to check types stays the same no matter how big the numbers are because it only looks at the type, not the value size.

Input Size (n)	Approx. Operations
10	2 type checks + 1 addition
100	2 type checks + 1 addition
1000	2 type checks + 1 addition

Pattern observation: The number of operations does not grow with input size; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means the time to run this code stays the same no matter how big the input numbers are.

Common Mistake

[X] Wrong: "Checking types slows down the program a lot as inputs get bigger."

[OK] Correct: Type checks look only at the kind of data, not its size, so they take the same time regardless of input size.

Interview Connect

Understanding how dynamic and strong typing affect program speed helps you explain how Ruby handles data behind the scenes, a useful skill for writing clear and efficient code.

Self-Check

"What if we changed the type checks to happen inside a loop over a list of inputs? How would the time complexity change?"

Practice

1. Which statement best describes Ruby's typing system?

easy

A. Ruby is dynamically typed and strongly typed.

B. Ruby is statically typed and weakly typed.

C. Ruby is statically typed and strongly typed.

D. Ruby is dynamically typed and weakly typed.

Solution

1. Step 1: Understand dynamic typing

   Dynamic typing means variables can hold any type and change types anytime during execution.

2. Step 2: Understand strong typing

   Strong typing means the language prevents mixing incompatible types without explicit conversion.

3. Final Answer:

   Ruby is dynamically typed and strongly typed. -> Option A

4. Quick Check:

   Dynamic + Strong = C [OK]

Hint: Remember Ruby allows type changes but checks type safety [OK]

Common Mistakes:

• Confusing dynamic with static typing
• Thinking Ruby allows unsafe type mixing
• Mixing weak and strong typing concepts

2. Which Ruby code snippet shows dynamic typing in action?

easy

A. x = 10; x = "hello"

B. int x = 10; x = "hello"

C. var x: Integer = 10; x = "hello"

D. let x = 10; x = true

Solution

1. Step 1: Identify Ruby syntax

   Ruby allows assigning different types to the same variable without error.

2. Step 2: Check each option

   x = 10; x = "hello" uses Ruby syntax and changes x from integer to string, showing dynamic typing.

3. Final Answer:

   x = 10; x = "hello" -> Option A

4. Quick Check:

   Variable changes type dynamically = A [OK]

Hint: Look for variable reassignment with different types in Ruby syntax [OK]

Common Mistakes:

• Choosing code with static typing syntax
• Confusing variable declaration styles
• Ignoring language-specific syntax rules

3. What will be the output of this Ruby code?

def add(a, b)
  a + b
end

puts add(5, "10")

medium

A. 15

B. TypeError

C. 510

D. nil

Solution

1. Step 1: Analyze the method call

   The method add tries to add an integer (5) and a string ("10") using + operator.

2. Step 2: Understand Ruby's strong typing

   Ruby does not automatically convert types for +; adding integer and string causes a TypeError.

3. Final Answer:

   TypeError -> Option B

4. Quick Check:

   Strong typing prevents int + string = B [OK]

Hint: Adding different types without conversion causes TypeError [OK]

Common Mistakes:

• Assuming automatic string conversion
• Expecting concatenation of numbers and strings
• Ignoring Ruby's type safety rules

4. Identify the error in this Ruby code:

def multiply(x, y)
  x * y
end

result = multiply(3, "4")
puts result

medium

A. NameError for undefined variable

B. SyntaxError due to method definition

C. No error, outputs 12

D. TypeError due to multiplying integer and string

Solution

1. Step 1: Check method parameters and call

   The method multiply is called with an integer (3) and a string ("4").

2. Step 2: Understand Ruby's type rules for *

   Multiplying integer by string without conversion causes a TypeError in Ruby.

3. Final Answer:

   TypeError due to multiplying integer and string -> Option D

4. Quick Check:

   Strong typing blocks int * string = A [OK]

Hint: Check operand types for * operator to avoid TypeError [OK]

Common Mistakes:

• Thinking Ruby auto-converts string to integer
• Assuming no error on mixed types
• Confusing SyntaxError with TypeError

5. You want to write a Ruby method that adds two values but safely handles if one is a string representing a number. Which approach best uses Ruby's dynamic and strong typing?

hard

A. Convert both to strings and concatenate.

B. Add values directly without conversion.

C. Convert both to integers before adding using to_i method.

D. Use static type declarations for parameters.

Solution

1. Step 1: Understand dynamic typing flexibility

   Ruby variables can hold any type, so inputs can be string or integer.

2. Step 2: Use strong typing safety

   To avoid TypeError, convert strings to integers explicitly before adding.

3. Step 3: Evaluate options

   Converting both to integers using to_i before adding is safe. Adding directly risks TypeError. Static type declarations are invalid in Ruby. Converting to strings performs concatenation instead of addition.

4. Final Answer:

   Convert both to integers before adding using to_i method. -> Option C

5. Quick Check:

   Dynamic + Strong typing = explicit conversion [OK]

Hint: Convert strings to numbers before math to avoid errors [OK]

Common Mistakes:

• Ignoring type conversion before arithmetic
• Assuming Ruby auto-converts types
• Using static typing syntax in Ruby