Impara Refactoring Loops into Methods | Functions Returning Arrays and Refactoring Loops

When writing programs, you often encounter situations where similar or identical blocks of code appear in multiple places. This is especially common with loops that perform the same task, like printing every element in an array. Such repetition can make your code harder to read, maintain, and update. Instead of copying and pasting the same loop in different parts of your program, you can refactor the code by moving the repeated logic into a method. Refactoring means restructuring your code without changing its external behavior, making it cleaner and more organized.

Before Refactoring

Program.cs


              1234567891011121314151617181920212223
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] numbers = { 2, 4, 6, 8 };

            // Print elements (first time)
            for (int i = 0; i < numbers.Length; i++)
            {
                System.Console.WriteLine(numbers[i]);
            }

            // Print elements (second time)
            for (int i = 0; i < numbers.Length; i++)
            {
                System.Console.WriteLine(numbers[i]);
            }
        }
    }
}

After Refactoring

Program.cs


              123456789101112131415161718192021
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] numbers = { 2, 4, 6, 8 };

            PrintArray(numbers);
            PrintArray(numbers);
        }

        public static void PrintArray(int[] arr)
        {
            for (int i = 0; i < arr.Length; i++)
            {
                System.Console.WriteLine(arr[i]);
            }
        }
    }
}

Refactoring repeated code into methods helps you write programs that are easier to read and understand. When you give a descriptive name to a method, anyone reading your code can immediately tell what the method does without digging into the details of the loop. This also makes your code easier to maintain — if you need to change how you print the array, you only need to update the method in one place. Reducing repetition also lowers the chance of errors, since you avoid having to make the same change in multiple locations.

Program.cs


              12345678910111213141516171819202122
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] scores = { 10, 20, 30, 40 };
            int total = SumArray(scores);
            System.Console.WriteLine("Sum: " + total);
        }

        public static int SumArray(int[] arr)
        {
            int sum = 0;
            for (int i = 0; i < arr.Length; i++)
            {
                sum += arr[i];
            }
            return sum;
        }
    }
}

This example shows that refactoring is not only useful for printing data, but also for calculations. By moving the loop that calculates the sum into a method, you make your code easier to reuse and maintain, while keeping the main program clean and focused.

1. What is the main advantage of refactoring repeated code into a method?

2. Which of the following is NOT a benefit of using methods for repetitive tasks?

Tutto è chiaro?

Grazie per i tuoi commenti!

Sezione 2. Capitolo 3

Chieda ad AI

Chieda pure quello che desidera o provi una delle domande suggerite per iniziare la nostra conversazione

Suggested prompts:

Can you show an example of code before and after refactoring?

What are some best practices for naming methods when refactoring?

How do I decide which code should be refactored into a method?

Scorri per mostrare il menu

Before Refactoring

Program.cs


              1234567891011121314151617181920212223
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] numbers = { 2, 4, 6, 8 };

            // Print elements (first time)
            for (int i = 0; i < numbers.Length; i++)
            {
                System.Console.WriteLine(numbers[i]);
            }

            // Print elements (second time)
            for (int i = 0; i < numbers.Length; i++)
            {
                System.Console.WriteLine(numbers[i]);
            }
        }
    }
}

After Refactoring

Program.cs


              123456789101112131415161718192021
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] numbers = { 2, 4, 6, 8 };

            PrintArray(numbers);
            PrintArray(numbers);
        }

        public static void PrintArray(int[] arr)
        {
            for (int i = 0; i < arr.Length; i++)
            {
                System.Console.WriteLine(arr[i]);
            }
        }
    }
}

Program.cs


              12345678910111213141516171819202122
            
namespace ConsoleApp
{
    public class Program
    {
        public static void Main(string[] args)
        {
            int[] scores = { 10, 20, 30, 40 };
            int total = SumArray(scores);
            System.Console.WriteLine("Sum: " + total);
        }

        public static int SumArray(int[] arr)
        {
            int sum = 0;
            for (int i = 0; i < arr.Length; i++)
            {
                sum += arr[i];
            }
            return sum;
        }
    }
}

1. What is the main advantage of refactoring repeated code into a method?

2. Which of the following is NOT a benefit of using methods for repetitive tasks?

Tutto è chiaro?

Grazie per i tuoi commenti!

Sezione 2. Capitolo 3