Why records were introduced in C Sharp (C#) - See It in Action

Understanding Why Records Were Introduced in C#

📖 Scenario: Imagine you want to store information about a book in a library system. You want to keep the title and author together and easily compare two books to see if they are the same.

🎯 Goal: You will create a simple data structure to hold book information and learn why C# introduced record types to make this easier and clearer.

📋 What You'll Learn

Create a class to hold book information with properties for title and author

Create a record to hold book information with the same properties

Compare two instances of the class and two instances of the record

Print the results of the comparisons to see the difference

💡 Why This Matters

🌍 Real World

Records are useful when you want to store data like user profiles, settings, or messages where comparing content matters more than comparing object references.

💼 Career

Understanding records helps you write cleaner, safer code in C# applications, especially in domains like web development, APIs, and data processing.

1

Create a class called BookClass with Title and Author properties

Write a class named BookClass with two public string properties: Title and Author. Use auto-properties with get and set.

C Sharp (C#)

// Your code here

Hint

Use public class BookClass and add two properties with get; set;.

2

Create a record called BookRecord with Title and Author properties

Write a record named BookRecord with two public string properties: Title and Author. Use positional parameters in the record declaration.

C Sharp (C#)

public class BookClass
{
    public string Title { get; set; }
    public string Author { get; set; }
}

// Your code here

Hint

Use public record BookRecord(string Title, string Author); to create a record with two properties.

3

Create two instances of BookClass and two instances of BookRecord with the same data

Create two BookClass objects named book1 and book2 with Title = "C# Guide" and Author = "Jane Doe". Also create two BookRecord objects named record1 and record2 with the same values.

C Sharp (C#)

public class BookClass
{
    public string Title { get; set; }
    public string Author { get; set; }
}

public record BookRecord(string Title, string Author);

// Your code here

Hint

Create objects using new and assign the exact values for Title and Author.

4

Compare the two BookClass objects and the two BookRecord objects and print the results

Use Console.WriteLine to print the result of book1 == book2 and record1 == record2. This will show how equality works differently for classes and records.

C Sharp (C#)

public class BookClass
{
    public string Title { get; set; }
    public string Author { get; set; }
}

public record BookRecord(string Title, string Author);

BookClass book1 = new BookClass { Title = "C# Guide", Author = "Jane Doe" };
BookClass book2 = new BookClass { Title = "C# Guide", Author = "Jane Doe" };

BookRecord record1 = new BookRecord("C# Guide", "Jane Doe");
BookRecord record2 = new BookRecord("C# Guide", "Jane Doe");

// Your code here

Hint

Use Console.WriteLine(book1 == book2); and Console.WriteLine(record1 == record2); inside a Main method.

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