Why records were introduced in C Sharp (C#) - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a record type named Person.

C Sharp (C#)

public [1] Person(string Name, int Age);

Drag options to blanks, or click blank then click option'

Arecord

Bclass

Cstruct

Dinterface

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'class' instead of 'record' will create a normal class without value equality.

Using 'struct' creates a value type but lacks record features.

The record keyword declares a record type, which is a reference type with value-based equality.

2fill in blank

medium

Complete the code to create a new Person record with name 'Alice' and age 30.

C Sharp (C#)

var person = new Person([1], 30);

Drag options to blanks, or click blank then click option'

A"Alice"

BAlice

Cperson.Name

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around string literals causes errors.

Using variable names instead of string literals.

String values must be enclosed in double quotes in C#.

3fill in blank

hard

Fix the error in comparing two Person records for equality.

C Sharp (C#)

bool areEqual = person1 [1] person2;

Drag options to blanks, or click blank then click option'

Aequals

B!=

C==

D=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' instead of '==' causes assignment, not comparison.

Using 'equals' is not a valid operator in C#.

Records support value-based equality using the == operator.

4fill in blank

hard

Fill in the blank to create a copy of a Person record with a changed Age.

C Sharp (C#)

var olderPerson = person with [1];

Drag options to blanks, or click blank then click option'

A[ Age = 31 ]

B( Age = 31 )

C< Age = 31 >

D{ Age = 31 }

Attempts:

3 left

💡 Hint

Common Mistakes

Using parentheses or brackets instead of braces causes syntax errors.

Omitting braces entirely is invalid syntax.

The with expression uses braces to specify property changes in a record copy.

5fill in blank

hard

Fill all three blanks to define a record with positional parameters and override ToString method.

C Sharp (C#)

public [1] Person(string Name, int Age) {
    public override string ToString() => $"[2] is [3] years old.";
}

Drag options to blanks, or click blank then click option'

Arecord

Bclass

CName

DAge

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'class' instead of 'record' loses record benefits.

Using incorrect property names in the string causes errors.

Records are declared with record. The ToString method uses the properties Name and Age to display info.

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