Value type copying behavior in C Sharp (C#) - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of struct value copy

What is the output of this C# code?

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);

C Sharp (C#)

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);

A 0

B 20

C 5

D Compilation error

💡 Hint

Remember that structs are value types and copying creates a new independent copy.

In C#, structs are value types. When you assign p1 to p2, a copy of the data is made. Changing p2.X does not affect p1.X, so p1.X remains 5.

❓ Predict Output

intermediate

Effect of modifying a copied value type

Consider this code:

int a = 10;
int b = a;
b = 30;
Console.WriteLine(a);

What will be printed?

C Sharp (C#)

int a = 10;
int b = a;
b = 30;
Console.WriteLine(a);

A 30

B 10

C 0

D Compilation error

💡 Hint

int is a value type, so assignment copies the value.

Assigning b = a copies the value 10. Changing b to 30 does not affect a, so a remains 10.

❓ Predict Output

advanced

Value type in method parameter behavior

What is the output of this code?

struct Number { public int Value; }
void Change(Number n) { n.Value = 100; }
Number num = new Number { Value = 50 };
Change(num);
Console.WriteLine(num.Value);

C Sharp (C#)

struct Number { public int Value; }
void Change(Number n) { n.Value = 100; }
Number num = new Number { Value = 50 };
Change(num);
Console.WriteLine(num.Value);

A Compilation error

B 100

C 0

D 50

💡 Hint

Value types are passed by value by default.

The method Change receives a copy of num. Modifying n.Value changes only the copy, so num.Value remains 50.

❓ Predict Output

advanced

Effect of ref keyword on value type parameter

What will this code print?

struct Data { public int X; }
void Modify(ref Data d) { d.X = 99; }
Data data = new Data { X = 10 };
Modify(ref data);
Console.WriteLine(data.X);

C Sharp (C#)

struct Data { public int X; }
void Modify(ref Data d) { d.X = 99; }
Data data = new Data { X = 10 };
Modify(ref data);
Console.WriteLine(data.X);

A 99

B Compilation error

C 0

D 10

💡 Hint

The ref keyword passes the value type by reference, allowing modification.

Using ref passes the struct by reference, so changes inside Modify affect the original data. data.X becomes 99.

🧠 Conceptual

expert

Understanding boxing and value type copying

Which statement best describes what happens when a value type is boxed in C#?

A A reference type object is created on the heap containing a copy of the value type data.

B The value type is passed by reference to avoid copying.

C The original value type is converted into a reference type without copying data.

D The value type is converted into a pointer to the original data.

💡 Hint

Boxing involves creating an object on the heap.

Boxing copies the value type data into a new object on the heap, which is a reference type. This allows value types to be treated as objects.

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