Bird
Raised Fist0
Rubyprogramming~15 mins

Match operator (=~) in Ruby - Mini Project: Build & Apply

Choose your learning style10 modes available
Using the Match Operator (=~) in Ruby
📖 Scenario: You are working on a simple text analyzer that checks if certain words appear in sentences. This is useful for filtering messages or searching for keywords.
🎯 Goal: Build a Ruby program that uses the match operator =~ to find if a word exists inside a sentence.
📋 What You'll Learn
Create a variable called sentence with a specific string.
Create a variable called word with a specific string.
Use the match operator =~ to check if word is in sentence.
Print the result of the match operation.
💡 Why This Matters
🌍 Real World
Searching for keywords in text messages, logs, or user input is common in many apps.
💼 Career
Understanding how to find patterns in text is useful for roles in software development, data analysis, and quality assurance.
Progress0 / 4 steps
1
Create the sentence variable
Create a variable called sentence and set it to the string "The quick brown fox jumps over the lazy dog".
Ruby
Hint

Use = to assign the string to sentence.

2
Create the word variable
Create a variable called word and set it to the string "fox".
Ruby
Hint

Assign the string "fox" to the variable word.

3
Use the match operator to find the word
Create a variable called position and set it to the result of sentence =~ /#{word}/ to find the position of word in sentence.
Ruby
Hint

Use =~ with a regular expression containing word inside slashes.

4
Print the match result
Print the value of the variable position using puts.
Ruby
Hint

Use puts position to display the index where the word starts.

Practice

(1/5)
1. What does the Ruby operator =~ do when used like string =~ /pattern/?
easy
A. Splits the string into an array based on the pattern
B. Returns true if the pattern is found, false otherwise
C. Replaces the pattern in the string with another string
D. Returns the index where the pattern starts in the string or nil if not found

Solution

  1. Step 1: Understand the operator's purpose

    The =~ operator checks if a regex pattern matches anywhere in the string.
  2. Step 2: Know the return value

    It returns the index of the first match or nil if no match is found.
  3. Final Answer:

    Returns the index where the pattern starts in the string or nil if not found -> Option D
  4. Quick Check:

    =~ returns index or nil [OK]
Hint: Remember: =~ returns index or nil, not true/false [OK]
Common Mistakes:
  • Thinking it returns true or false
  • Confusing it with string replacement
  • Assuming it splits the string
2. Which of the following is the correct syntax to check if the string "hello123" contains digits using the match operator?
easy
A. "hello123" =~ /\d+/
B. "hello123" =~ "\d+"
C. "hello123" =~ /\w+/
D. "hello123" =~ /[a-z]+/i

Solution

  1. Step 1: Identify correct regex syntax

    The pattern to match digits is /\d+/, which is a regex literal in Ruby.
  2. Step 2: Match operator requires regex, not string

    The =~ operator expects a regex on the right side, so /\d+/ is correct, not a string.
  3. Final Answer:

    "hello123" =~ /\d+/ -> Option A
  4. Quick Check:

    Regex literal with =~ is correct [OK]
Hint: Use slashes /pattern/ for regex with =~ operator [OK]
Common Mistakes:
  • Using a string instead of regex on right side
  • Confusing \d with \w for digits
  • Missing regex delimiters
3. What will be the output of this Ruby code?
text = "OpenAI GPT-4"
index = text =~ /GPT/
puts index
medium
A. nil
B. 0
C. 7
D. SyntaxError

Solution

  1. Step 1: Locate the pattern in the string

    The string is "OpenAI GPT-4". The substring "GPT" starts at index 7 (counting from 0).
  2. Step 2: Understand what =~ returns

    The operator returns the index of the first match, so it returns 7.
  3. Final Answer:

    7 -> Option C
  4. Quick Check:

    Index of "GPT" in string = 7 [OK]
Hint: Count characters from zero to find match index [OK]
Common Mistakes:
  • Counting from 1 instead of 0
  • Expecting true/false instead of index
  • Assuming nil if unsure
4. Identify the error in this Ruby code snippet:
str = "test123"
result = str =~ "\d+"
puts result
medium
A. Using a string instead of a regex pattern with =~
B. Missing parentheses around =~ operator
C. Incorrect variable name 'str'
D. Using puts instead of print

Solution

  1. Step 1: Check the right side of =~ operator

    The code uses a string "\d+" instead of a regex literal /\d+/.
  2. Step 2: Understand =~ expects regex

    The match operator requires a regex pattern, so using a string causes a TypeError or unexpected behavior.
  3. Final Answer:

    Using a string instead of a regex pattern with =~ -> Option A
  4. Quick Check:

    Right side of =~ must be regex [OK]
Hint: Always use /pattern/ regex, not strings, with =~ [OK]
Common Mistakes:
  • Using strings instead of regex
  • Thinking parentheses are needed
  • Confusing puts with print
5. Given the array words = ["cat", "dog", "bird", "cow"], which code snippet uses the match operator to find the first word containing the letter 'i' and returns its index in the array?
hard
A. words.find { |w| w =~ /i/ }
B. words.find_index { |w| w =~ /i/ }
C. words.index { |w| w.include?('i') }
D. words.select { |w| w =~ /i/ }

Solution

  1. Step 1: Understand the goal

    We want the index of the first word containing 'i'.
  2. Step 2: Use find_index with match operator

    find_index returns the index of the first element where the block is true. Using w =~ /i/ returns index or nil, so truthy means match found.
  3. Step 3: Check other options

    words.index { |w| w.include?('i') } uses include? which works but is not using the match operator. words.find { |w| w =~ /i/ } returns the word, not index. words.select { |w| w =~ /i/ } returns all matches, not index.
  4. Final Answer:

    words.find_index { |w| w =~ /i/ } -> Option B
  5. Quick Check:

    find_index with =~ returns correct index [OK]
Hint: Use find_index with =~ to get index of first match [OK]
Common Mistakes:
  • Using find instead of find_index for index
  • Using include? instead of =~
  • Expecting select to return single index
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard