Struct declaration and behavior in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Struct declaration and behavior

Declare struct type

↓

Create struct variable

↓

Assign values to fields

↓

Use struct variable

↓

Copy struct variable?

Yes↓

Create independent copy

↓

Modify copy does NOT affect original

↓

End

This flow shows how a struct is declared, used, and how copying creates independent values.

Execution Sample

C Sharp (C#)

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

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

This code declares a struct Point, creates one instance, copies it, and changes the copy's field.

Execution Table

Step	Action	Variable States	Notes
1	Declare struct Point with fields X and Y	No variables yet	Struct type created
2	Create p1 with X=1, Y=2	p1: {X=1, Y=2}	p1 holds values 1 and 2
3	Copy p1 to p2	p1: {X=1, Y=2}, p2: {X=1, Y=2}	p2 is a separate copy of p1
4	Change p2.X to 5	p1: {X=1, Y=2}, p2: {X=5, Y=2}	p2 changed, p1 unchanged
5	End	p1: {X=1, Y=2}, p2: {X=5, Y=2}	Struct copy is independent

💡 Execution ends after modifying p2; p1 remains unchanged because structs are value types.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
p1	undefined	{X=1, Y=2}	{X=1, Y=2}	{X=1, Y=2}	{X=1, Y=2}
p2	undefined	undefined	{X=1, Y=2}	{X=5, Y=2}	{X=5, Y=2}

Key Moments - 3 Insights

Why does changing p2.X not affect p1.X?

Because structs are value types, copying p1 to p2 creates a new independent copy. See execution_table step 4 where p2.X changes but p1.X stays the same.

Is the struct variable a reference or a value?

Struct variables hold values directly, not references. This is why copying creates independent copies, as shown in execution_table step 3.

What happens if we assign one struct variable to another?

A full copy of the struct's data is made. Both variables then hold separate copies, so changes to one do not affect the other (execution_table step 3 and 4).

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the value of p1.X?

A 0

B 5

C 1

D Undefined

💡 Hint

Check the Variable States column at step 4 in execution_table.

At which step does p2 get its own copy of p1's data?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Look for the step where p2 is assigned values from p1 in execution_table.

If structs were reference types, what would happen when p2.X changes?

A p1.X would stay the same

B p1.X would also change

C p2.X would revert to p1.X

D Compilation error

💡 Hint

Think about how reference types share the same data, unlike value types shown in variable_tracker.

Concept Snapshot

struct StructName {
  public Type Field1;
  public Type Field2;
}

- Structs are value types.
- Assigning copies all data.
- Changes to copies do not affect originals.

Full Transcript

This visual trace shows how a struct is declared and used in C#. First, the struct type Point is declared with two integer fields X and Y. Then, a variable p1 of type Point is created and initialized with X=1 and Y=2. Next, p1 is copied to p2, creating an independent copy. When p2.X is changed to 5, p1.X remains 1, showing that structs hold values directly and copying creates separate instances. This behavior is different from reference types where variables share the same data. The key moments highlight why changes to copies do not affect originals and clarify that structs are value types. The quiz questions reinforce understanding of when copies happen and how values change during execution.

Practice

1. Which of the following statements about struct in C# is true?

easy

A. Structs support inheritance from other structs.

B. Structs are value types and are copied when assigned to a new variable.

C. Structs can have a parameterless constructor defined by the user.

D. Structs are reference types and stored on the heap.

Solution

1. Step 1: Understand struct type behavior

   Structs in C# are value types, meaning when you assign them to another variable, a copy is made.

2. Step 2: Check inheritance and constructors rules

   Structs cannot inherit from other structs or classes, and they cannot have user-defined parameterless constructors. They are stored on the stack, not the heap.

3. Final Answer:

   Structs are value types and are copied when assigned to a new variable. -> Option B

4. Quick Check:

   Struct = Value type copy [OK]

Hint: Remember: structs copy values, no inheritance, no default constructor [OK]

Common Mistakes:

• Thinking structs are reference types
• Assuming structs support inheritance
• Trying to define parameterless constructors in structs

2. Which of the following is the correct way to declare a struct named Point with two integer fields x and y?

easy

A. struct Point { public int x; public int y; }

B. class Point { int x; int y; }

C. struct Point { int x; int y; }

D. struct Point { int x; int y; void Point() {} }

Solution

1. Step 1: Check struct field accessibility

   Fields inside a struct should be declared with an access modifier like public to be accessible outside.

2. Step 2: Validate struct syntax

   struct Point { int x; int y; } misses access modifiers, so fields are private by default and not accessible. class Point { int x; int y; } uses class, not struct. struct Point { int x; int y; void Point() {} } tries to define a constructor with void return type, which is invalid.

3. Final Answer:

   struct Point { public int x; public int y; } -> Option A

4. Quick Check:

   Struct fields need public modifier [OK]

Hint: Use public fields in structs for external access [OK]

Common Mistakes:

• Omitting access modifiers on struct fields
• Confusing struct with class keyword
• Defining constructors with void return type

3. What is the output of the following 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);

medium

A. 20

B. 10

C. 5

D. Compilation error

Solution

1. Step 1: Understand struct assignment behavior

   Assigning p1 to p2 copies the values because structs are value types.

2. Step 2: Analyze modification effect

   Changing p2.X to 20 does not affect p1.X, which remains 5.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   Struct copy means original unchanged [OK]

Hint: Struct assignment copies values, original stays same [OK]

Common Mistakes:

• Assuming structs behave like reference types
• Expecting p1.X to change after modifying p2.X
• Confusing output with Y field value

4. Identify the error in the following struct declaration:

struct Rectangle {
  public int Width;
  public int Height;
  public Rectangle() { Width = 0; Height = 0; }
}

medium

A. Structs must inherit from System.ValueType explicitly.

B. Structs cannot have any constructors.

C. Fields must be private in structs.

D. Parameterless constructors are not allowed in structs.

Solution

1. Step 1: Recall struct constructor rules

   Structs cannot have user-defined parameterless constructors; the compiler provides a default one.

2. Step 2: Check other options

   Structs can have constructors with parameters, fields can be public, and inheritance from System.ValueType is implicit.

3. Final Answer:

   Parameterless constructors are not allowed in structs. -> Option D

4. Quick Check:

   No user parameterless constructor in struct [OK]

Hint: Structs get default parameterless constructor automatically [OK]

Common Mistakes:

• Trying to define parameterless constructor in struct
• Thinking structs must inherit explicitly
• Believing fields must be private

5. You want to create a struct Color that stores red, green, and blue values as bytes. You also want to ensure that when you assign one Color variable to another, changes to the second do not affect the first. Which approach is correct?

hard

A. Declare Color as a struct with public byte fields and assign normally.

B. Declare Color as a class with public byte fields and assign normally.

C. Declare Color as a struct but use pointers to share data.

D. Declare Color as a class and override the assignment operator.

Solution

1. Step 1: Understand value vs reference types

   Structs are value types, so assigning one struct variable to another copies the data, preventing shared changes.

2. Step 2: Evaluate options for data isolation

   Using a class would create reference types, so changes to one variable affect the other. Using pointers or overriding assignment is unnecessary and complex.

3. Final Answer:

   Declare Color as a struct with public byte fields and assign normally. -> Option A

4. Quick Check:

   Struct assignment copies data, no shared changes [OK]

Hint: Use struct for independent copies of small data [OK]

Common Mistakes:

• Using class instead of struct for value copy
• Trying to share data with pointers unnecessarily
• Overriding assignment operator in class (not allowed)