Why records were introduced in C Sharp (C#)

Introduction

Records were introduced to make it easier to create simple data containers that hold values and compare them by their content, not by their location in memory.

When you want to store data like a person's name and age without writing a lot of code.

When you need to compare two objects to see if they have the same data, not if they are the same object.

When you want your data objects to be easy to read and write with less chance of mistakes.

When you want to create immutable objects that cannot be changed after creation.

When you want built-in support for copying objects with some changes.

Syntax

C Sharp (C#)

public record Person(string Name, int Age);

This syntax creates a record with two properties: Name and Age.

Records automatically provide value-based equality and useful methods like ToString.

Examples

A simple record to hold X and Y coordinates.

C Sharp (C#)

public record Point(int X, int Y);

A record with properties that can only be set during creation (immutable).

C Sharp (C#)

public record Person
{
    public string Name { get; init; }
    public int Age { get; init; }
}

Shows that two records with the same data are equal.

C Sharp (C#)

var p1 = new Person("Alice", 30);
var p2 = new Person("Alice", 30);
Console.WriteLine(p1 == p2);

Sample Program

This program shows how records print their data and compare by content, not by reference.

C Sharp (C#)

public record Person(string Name, int Age);

class Program
{
    static void Main()
    {
        var person1 = new Person("John", 25);
        var person2 = new Person("John", 25);
        var person3 = new Person("Jane", 30);

        Console.WriteLine(person1); // Prints the data nicely
        Console.WriteLine(person1 == person2); // True because data is same
        Console.WriteLine(person1 == person3); // False because data differs
    }
}

Important Notes

Records are great for data that should not change after creation.

They help avoid writing extra code for equality and string display.

Records use init properties to allow setting values only when creating the object.

Summary

Records simplify creating data containers with less code.

They compare objects by their data, not by memory location.

Records provide built-in support for immutability and easy copying.

Practice

1. Why were records introduced in C#?

easy

A. To simplify creating data containers with less code

B. To improve performance of loops

C. To replace classes entirely

D. To add new syntax for exception handling

Solution

1. Step 1: Understand the purpose of records

   Records were introduced to make it easier to create simple data containers without writing a lot of boilerplate code.

2. Step 2: Compare with other options

   Options B, C, and D do not relate to the main purpose of records. They do not improve loops, replace classes entirely, or add exception handling syntax.

3. Final Answer:

   To simplify creating data containers with less code -> Option A

4. Quick Check:

   Records simplify data containers = A [OK]

Hint: Records are for easy data containers, not loops or exceptions [OK]

Common Mistakes:

• Thinking records replace all classes
• Confusing records with performance features
• Assuming records add exception handling

2. Which of the following is the correct syntax to declare a positional record in C#?

easy

A. record Person { string Name; int Age; }

B. class Person { string Name; int Age; }

C. struct Person(string Name, int Age);

D. record Person(string Name, int Age);

Solution

1. Step 1: Recall record declaration syntax

   Records can be declared using the concise syntax: record Person(string Name, int Age); which defines positional properties.

2. Step 2: Check other options

   class Person { string Name; int Age; } is a class, not a record. struct Person(string Name, int Age); is a struct, not a record. record Person { string Name; int Age; } uses body syntax with braces, not the positional syntax with parentheses.

3. Final Answer:

   record Person(string Name, int Age); -> Option D

4. Quick Check:

   Positional record syntax uses parentheses = D [OK]

Hint: Records with positional params use parentheses, not braces [OK]

Common Mistakes:

• Using class instead of record keyword
• Using braces instead of parentheses for positional records
• Confusing struct with record syntax

3. What will be the output of this code?

record Point(int X, int Y);
var p1 = new Point(1, 2);
var p2 = new Point(1, 2);
Console.WriteLine(p1 == p2);

medium

A. False

B. Compilation error

C. True

D. Runtime exception

Solution

1. Step 1: Understand record equality behavior

   Records compare by their data values, so two records with the same values are equal.

2. Step 2: Analyze the code output

   Since p1 and p2 have the same X and Y values, p1 == p2 returns true.

3. Final Answer:

   True -> Option C

4. Quick Check:

   Records compare data equality = True [OK]

Hint: Records compare by data, so same values mean equality [OK]

Common Mistakes:

• Assuming == compares references for records
• Expecting false because of different objects
• Thinking code causes error or exception

4. Identify the error in this record declaration:

record Person(string Name, int Age)

medium

A. Missing semicolon after record name

B. Records cannot have any members inside braces

C. Records cannot have public fields, only properties

D. Record keyword must be lowercase

Solution

1. Step 1: Check positional record syntax

   Positional records require a semicolon after the parameter list: record Person(string Name, int Age);.

2. Step 2: Validate other options

   Records cannot have any members inside braces is incorrect as there are no braces used. Records cannot have public fields, only properties is wrong because no fields are declared here. Record keyword must be lowercase is incorrect as the keyword is already lowercase.

3. Final Answer:

   Missing semicolon after record name -> Option A

4. Quick Check:

   Positional records require ; after params [OK]

Hint: Positional records require a semicolon after the parameters [OK]

Common Mistakes:

• Forgetting semicolon in positional record declaration
• Using braces {} for positional records
• Confusing with struct syntax

5. You want to create an immutable data container for a book with title and author, and easily create modified copies. Which feature introduced in C# helps you do this with minimal code?

hard

A. Classes with private setters

B. Records with init-only properties

C. Structs with readonly fields

D. Interfaces with default implementations

Solution

1. Step 1: Identify the need for immutability and easy copying

   Records provide built-in support for immutability using init-only properties and a with expression to create modified copies easily.

2. Step 2: Compare with other options

   Classes with private setters require more code and do not support with expressions. Structs are value types but less convenient for copying. Interfaces do not hold data.

3. Final Answer:

   Records with init-only properties -> Option B

4. Quick Check:

   Immutability + easy copying = Records [OK]

Hint: Use records for immutable data and easy copies [OK]

Common Mistakes:

• Choosing classes instead of records for immutability
• Confusing structs with records for copying
• Thinking interfaces hold data