Object type annotation inline in Typescript - Time & Space Complexity

Time Complexity: Object type annotation inline

O(1)

Understanding Time Complexity

When we write object type annotations inline in TypeScript, we want to know how this affects the time it takes for the program to run.

We ask: How does the program's work grow as the object size or usage grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function printUser(user: { name: string; age: number; active: boolean }) {
  console.log(`Name: ${user.name}`);
  console.log(`Age: ${user.age}`);
  console.log(`Active: ${user.active}`);
}

const user = { name: "Alice", age: 30, active: true };
printUser(user);
    

This code defines a function with an inline object type annotation and prints its properties.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing and printing each property of the object once.
• How many times: Exactly three times, once per property.

How Execution Grows With Input

As the number of properties in the object grows, the number of operations remains constant (always 3 accesses).

Input Size (n)	Approx. Operations
3	3
10	3
100	3

Pattern observation: The work stays constant regardless of the number of properties since only specific named properties are accessed.

Final Time Complexity

Time Complexity: O(1)

This means the time to run remains constant as the number of object properties increases.

Common Mistake

[X] Wrong: "Using inline object type annotations makes the code slower because it adds extra work at runtime."

[OK] Correct: Type annotations are only for the developer and compiler; they do not affect the running speed of the program.

Interview Connect

Understanding how your code scales with input size helps you write clear and efficient programs, a skill valued in many coding challenges and real projects.

Self-Check

"What if the function processed an array of such objects instead of just one? How would the time complexity change?"

Practice

1. What does inline object type annotation in TypeScript do?
let user: { name: string; age: number };

easy

A. It defines the shape of the object directly where it is used.

B. It creates a new class named user.

C. It converts the object to a JSON string.

D. It declares a function that returns an object.

Solution

1. Step 1: Understand inline object type annotation

   Inline object type annotation specifies the properties and their types directly in the variable declaration.

2. Step 2: Analyze the example

   The example { name: string; age: number } tells TypeScript that user must have a string name and a number age.

3. Final Answer:

   It defines the shape of the object directly where it is used. -> Option A

4. Quick Check:

   Inline type annotation = direct object shape [OK]

Hint: Inline means type right where variable is declared [OK]

Common Mistakes:

• Thinking it creates a class
• Confusing with JSON conversion
• Assuming it declares a function

2. Which of the following is the correct syntax for inline object type annotation in TypeScript?

easy

A. let data: (id: number, title: string) = { id: 1, title: 'Book' };

B. let data = { id: number, title: string } = { id: 1, title: 'Book' };

C. let data: { id: number; title: string } = { id: 1, title: 'Book' };

D. let data: [number, string] = { id: 1, title: 'Book' };

Solution

1. Step 1: Identify correct inline object type syntax

   Inline object type annotation uses curly braces with property names and types, like { id: number; title: string }.

2. Step 2: Check each option

   let data: { id: number; title: string } = { id: 1, title: 'Book' }; correctly uses this syntax and assigns a matching object. Options A, B, and D use incorrect syntax or types.

3. Final Answer:

   let data: { id: number; title: string } = { id: 1, title: 'Book' }; -> Option C

4. Quick Check:

   Curly braces with property types = correct syntax [OK]

Hint: Use curly braces with property: type pairs [OK]

Common Mistakes:

• Using parentheses instead of braces
• Assigning types inside object literal
• Confusing arrays with objects

3. What will be the output of this TypeScript code?

function printUser(user: { name: string; age: number }) {
  console.log(`${user.name} is ${user.age} years old.`);
}
printUser({ name: 'Alice', age: 30 });

medium

A. Alice is 30 years old.

B. Error: Missing property age

C. Alice is undefined years old.

D. Error: Type mismatch in function argument

Solution

1. Step 1: Understand the function parameter type

   The function expects an object with name as string and age as number.

2. Step 2: Check the argument passed

   The argument { name: 'Alice', age: 30 } matches the expected type exactly.

3. Final Answer:

   Alice is 30 years old. -> Option A

4. Quick Check:

   Matching object type = correct output [OK]

Hint: Match object shape exactly to avoid errors [OK]

Common Mistakes:

• Passing missing or extra properties
• Using wrong types for properties
• Ignoring inline type annotation

4. Identify the error in this TypeScript code snippet:

let product: { id: number; name: string } = { id: 101, name: 'Pen', price: 5 };

medium

A. Missing semicolon after object declaration.

B. Extra property 'price' not allowed in inline type annotation.

C. Property 'id' should be a string, not number.

D. Object must be assigned to a function, not a variable.

Solution

1. Step 1: Check the declared type

   The type annotation allows only id and name properties.

2. Step 2: Compare with assigned object

   The object has an extra property price which is not declared in the type, causing an error.

3. Final Answer:

   Extra property 'price' not allowed in inline type annotation. -> Option B

4. Quick Check:

   Extra properties cause errors in inline types [OK]

Hint: Only use declared properties in inline object types [OK]

Common Mistakes:

• Adding extra properties not in type
• Ignoring TypeScript error messages
• Confusing semicolon placement

5. You want to write a function that accepts an object with a string title and an optional number year. Which inline type annotation is correct?

hard

A. function showBook(book: { title: string; year: number | undefined }) { console.log(book.title); }

B. function showBook(book: { title: string | number; year: number }) { console.log(book.title); }

C. function showBook(book: { title?: string; year: number }) { console.log(book.title); }

D. function showBook(book: { title: string; year?: number }) { console.log(book.title); }

Solution

1. Step 1: Understand optional properties in inline types

   Optional properties are marked with a question mark ? after the property name.

2. Step 2: Analyze each option

   function showBook(book: { title: string; year?: number }) { console.log(book.title); } correctly marks year as optional with year?: number. Other options either make title optional or use incorrect types.

3. Final Answer:

   function showBook(book: { title: string; year?: number }) { console.log(book.title); } -> Option D

4. Quick Check:

   Optional property uses ? after name [OK]

Hint: Use ? after property name for optional fields [OK]

Common Mistakes:

• Making required properties optional
• Using union types incorrectly
• Confusing optional with undefined type