Value type copying behavior in C Sharp (C#) - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a value type variable.

C Sharp (C#)

int [1] = 10;

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

Anumber

BrefNumber

CmyClass

Dobj

Attempts:

3 left

💡 Hint

Common Mistakes

Using names that imply reference types instead of value types.

The variable number is a simple value type variable of type int.

2fill in blank

medium

Complete the code to copy the value of one variable to another.

C Sharp (C#)

int a = 5;
int b = [1];

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

Aref a

Ba

C&a

Dnew int()

Attempts:

3 left

💡 Hint

Common Mistakes

Using reference or address operators which are invalid here.

Assigning b = a copies the value of a into b.

3fill in blank

hard

Fix the error in copying a struct value.

C Sharp (C#)

struct Point { public int X; public int Y; }

Point p1 = new Point { X = 1, Y = 2 };
Point p2 = [1];
p2.X = 5;

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

Ap1

B&p1

Cref p1

Dnew Point()

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to assign struct by reference using & or ref keywords.

Assigning p2 = p1 copies the struct value. Using &p1 or ref p1 is invalid here.

4fill in blank

hard

Fill both blanks to create a copy of a struct and modify it without changing the original.

C Sharp (C#)

struct Rectangle { public int Width; public int Height; }

Rectangle rect1 = new Rectangle { Width = 10, Height = 20 };
Rectangle rect2 = [1];
rect2.Width = [2];

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

Arect1

Brect2

C15

Drect1.Width

Attempts:

3 left

💡 Hint

Common Mistakes

Modifying the original struct instead of the copy.

Assigning rect2 = rect1 copies the value. Changing rect2.Width to 15 does not affect rect1.

5fill in blank

hard

Fill all three blanks to demonstrate that changing a copied value type does not affect the original.

C Sharp (C#)

struct Circle { public int Radius; }

Circle c1 = new Circle { Radius = 7 };
Circle c2 = [1];
c2.Radius = [2];
Console.WriteLine(c1.Radius == [3]);

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

Ac1

B10

C7

Dc2

Attempts:

3 left

💡 Hint

Common Mistakes

Assuming changing the copy changes the original.

Assigning c2 = c1 copies the value. Changing c2.Radius to 10 does not change c1.Radius, which remains 7.

Practice

1. What happens when you assign one value type variable to another in C#?

easy

A. The value type becomes a reference type automatically.

B. Both variables point to the same memory location.

C. A new independent copy of the value is created.

D. The original variable is deleted.

Solution

1. Step 1: Understand value type assignment

   Value types store data directly, so assigning one to another copies the data.

2. Step 2: Effect of copying value types

   Since a copy is made, changes to the new variable do not affect the original.

3. Final Answer:

   A new independent copy of the value is created. -> Option C

4. Quick Check:

   Value type assignment = copy value [OK]

Hint: Value types copy data, not references [OK]

Common Mistakes:

• Thinking value types share memory like reference types
• Assuming original changes when copy changes
• Confusing value types with reference types

2. Which of the following is the correct syntax to copy an int value type variable a to b in C#?

easy

A. int b == a;

B. int b = a;

C. int b := a;

D. int b => a;

Solution

1. Step 1: Review C# assignment syntax

   In C#, assignment uses a single equals sign = to copy values.

2. Step 2: Identify correct syntax for copying

   The statement int b = a; correctly copies the value of a into b.

3. Final Answer:

   int b = a; -> Option B

4. Quick Check:

   Assignment uses = in C# [OK]

Hint: Use single = for assignment in C# [OK]

Common Mistakes:

• Using double equals == which is for comparison
• Using := or => which are invalid here
• Confusing assignment with comparison operators

3. What is the output of the following C# code?

int x = 10;
int y = x;
y = 20;
Console.WriteLine(x);

medium

A. 10

B. 20

C. 0

D. Compilation error

Solution

1. Step 1: Trace variable assignments

   Variable x is 10, then y copies 10 from x.

2. Step 2: Change y and check x

   Changing y to 20 does not affect x because they are independent copies.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   Value type copy keeps original unchanged [OK]

Hint: Changing copy doesn't change original value [OK]

Common Mistakes:

• Assuming x changes when y changes
• Confusing value types with reference types
• Expecting runtime or compile errors

4. Identify the error in this code snippet related to value type copying:

struct Point { public int X; public int Y; }
Point p1 = new Point { X = 5, Y = 10 };
Point p2 = p1;
p2.X = 20;
Console.WriteLine(p1.X);

medium

A. No error; output is 5

B. Error: Cannot assign struct to another struct

C. Error: Cannot modify fields of a struct

D. Error: p2 is null

Solution

1. Step 1: Understand struct copying

   Structs are value types, so p2 = p1; copies the data.

2. Step 2: Check modification effect

   Changing p2.X does not affect p1.X, so p1.X remains 5.

3. Final Answer:

   No error; output is 5 -> Option A

4. Quick Check:

   Struct copy creates independent values [OK]

Hint: Struct assignment copies values, no errors [OK]

Common Mistakes:

• Thinking structs behave like reference types
• Expecting errors on struct field modification
• Assuming p2 is null after assignment

5. Given the struct and code below, what will be the output?

struct Score { public int Value; }
Score s1 = new Score { Value = 50 };
Score s2 = s1;
s2.Value += 10;
s1 = s2;
s2.Value = 100;
Console.WriteLine(s1.Value);

hard

A. 50

B. 100

C. Compilation error

D. 60

Solution

1. Step 1: Trace initial assignments and changes

   s1.Value starts at 50. s2 copies s1 (50). Then s2.Value increases by 10 to 60.

2. Step 2: Assign s2 back to s1 and change s2 again

   After s1 = s2;, s1.Value is 60. Changing s2.Value to 100 does not affect s1 because they are separate copies.

3. Final Answer:

   60 -> Option D

4. Quick Check:

   Value type copies keep values independent [OK]

Hint: Assigning structs copies values, later changes don't affect old copies [OK]

Common Mistakes:

• Assuming s1 changes when s2 changes after assignment
• Confusing struct copying with reference assignment
• Expecting compilation errors on struct assignments