Bird
Raised Fist0
Goprogramming~5 mins

Nested structs in Go - Time & Space Complexity

Choose your learning style10 modes available
Time Complexity: Nested structs
O(n)
Understanding Time Complexity

When working with nested structs in Go, it's important to understand how accessing and processing them affects the time your program takes.

We want to see how the time grows when we work through nested structs.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

type Address struct {
    City  string
    State string
}

type Person struct {
    Name    string
    Age     int
    Address Address
}

func printCities(people []Person) {
    for _, p := range people {
        fmt.Println(p.Address.City)
    }
}

This code loops through a list of people and prints the city from their nested Address struct.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

  • Primary operation: Looping through the slice of people.
  • How many times: Once for each person in the list.
How Execution Grows With Input

As the number of people increases, the number of times we print cities grows at the same rate.

Input Size (n)Approx. Operations
1010 prints
100100 prints
10001000 prints

Pattern observation: The work grows directly with the number of people.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of people.

Common Mistake

[X] Wrong: "Accessing nested structs makes the time complexity multiply or become slower than linear."

[OK] Correct: Accessing fields inside nested structs is a direct operation and does not add extra loops, so it does not increase the overall time complexity beyond the main loop.

Interview Connect

Understanding how nested structs affect time helps you explain your code clearly and shows you know how data structures impact performance.

Self-Check

"What if we added a nested loop inside the printCities function to loop over multiple addresses per person? How would the time complexity change?"

Practice

(1/5)
1. What is the main purpose of using nested structs in Go?
easy
A. To group related data together inside another struct
B. To create multiple independent structs
C. To make the program run faster
D. To avoid using functions

Solution

  1. Step 1: Understand struct grouping

    Nested structs allow one struct to contain another, grouping related data logically.
  2. Step 2: Compare options

    Creating multiple independent structs, making the program run faster, or avoiding functions do not describe grouping data inside structs.
  3. Final Answer:

    To group related data together inside another struct -> Option A
  4. Quick Check:

    Nested structs = Group related data [OK]
Hint: Think of nested structs as folders inside folders [OK]
Common Mistakes:
  • Confusing nested structs with separate structs
  • Thinking nested structs improve speed
  • Believing nested structs replace functions
2. Which of the following is the correct way to access the field City inside a nested struct Address within struct Person?
easy
A. person.City.Address
B. person->Address->City
C. person.Address.City
D. person.Address->City

Solution

  1. Step 1: Recall Go syntax for nested structs

    Access nested fields using dot notation: Outer.Inner.Field.
  2. Step 2: Evaluate options

    person.Address.City uses correct dot notation. Arrow syntax (->) is invalid in Go. person.City.Address reverses the order.
  3. Final Answer:

    person.Address.City -> Option C
  4. Quick Check:

    Dot notation = person.Address.City [OK]
Hint: Use dot notation to access nested fields [OK]
Common Mistakes:
  • Using arrow (->) instead of dot (.)
  • Reversing the order of fields
  • Trying to access nested fields directly without parent
3. What will be the output of the following Go code?
package main
import "fmt"
type Address struct {
    City string
    Zip  int
}
type Person struct {
    Name    string
    Address Address
}
func main() {
    p := Person{Name: "Anna", Address: Address{City: "Paris", Zip: 75000}}
    fmt.Println(p.Address.City)
}
medium
A. Anna
B. Paris
C. 75000
D. Address

Solution

  1. Step 1: Understand struct initialization

    Person struct has Name and Address fields. Address is initialized with City "Paris" and Zip 75000.
  2. Step 2: Identify printed field

    The code prints p.Address.City, which is "Paris".
  3. Final Answer:

    Paris -> Option B
  4. Quick Check:

    p.Address.City = Paris [OK]
Hint: Print nested field with dot notation [OK]
Common Mistakes:
  • Printing the wrong field like Name or Zip
  • Confusing struct field names
  • Expecting the whole struct to print
4. Identify the error in this Go code snippet involving nested structs:
package main
import "fmt"
type Engine struct {
    Power int
}
type Car struct {
    Model  string
    Engine Engine
}
func main() {
    c := Car{Model: "Sedan"}
    fmt.Println(c.Engine.Power)
}
medium
A. c.Engine.Power is zero value, no error
B. Car struct missing Engine field
C. Engine struct is not defined
D. Cannot print nested struct fields directly

Solution

  1. Step 1: Check struct definitions

    Engine and Car structs are defined correctly. Car has Engine field.
  2. Step 2: Analyze initialization and print

    Car instance c is created with Model only. Engine field is zero-valued (Power = 0). Printing c.Engine.Power prints 0 without error.
  3. Final Answer:

    c.Engine.Power is zero value, no error -> Option A
  4. Quick Check:

    Uninitialized nested struct fields have zero values [OK]
Hint: Uninitialized nested structs have zero values [OK]
Common Mistakes:
  • Assuming missing initialization causes error
  • Thinking nested fields can't be printed
  • Confusing missing fields with zero values
5. Given the structs below, how would you write a function FullAddress that returns a formatted string combining Street, City, and Zip from nested structs?
type Location struct {
    Street string
    City   string
}
type Address struct {
    Location Location
    Zip      int
}
hard
A. func FullAddress(a Address) string { return a.Street + ", " + a.City + " " + fmt.Sprint(a.Zip) }
B. func FullAddress(a Address) string { return a.Street + ", " + a.Location.City + " " + fmt.Sprint(a.Zip) }
C. func FullAddress(a Address) string { return a.Location.Street + ", " + a.City + " " + fmt.Sprint(a.Zip) }
D. func FullAddress(a Address) string { return a.Location.Street + ", " + a.Location.City + " " + fmt.Sprint(a.Zip) }

Solution

  1. Step 1: Identify nested fields

    Street and City are inside Location struct, which is nested inside Address.
  2. Step 2: Access nested fields correctly

    Use a.Location.Street and a.Location.City to access those fields, and a.Zip for Zip code.
  3. Step 3: Check options

    Only func FullAddress(a Address) string { return a.Location.Street + ", " + a.Location.City + " " + fmt.Sprint(a.Zip) } correctly accesses nested fields with dot notation.
  4. Final Answer:

    func FullAddress(a Address) string { return a.Location.Street + ", " + a.Location.City + " " + fmt.Sprint(a.Zip) } -> Option D
  5. Quick Check:

    Access nested fields with dot notation [OK]
Hint: Use dot notation for each nested level [OK]
Common Mistakes:
  • Accessing nested fields directly without parent struct
  • Mixing field names from different structs
  • Forgetting to convert int Zip to string
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard