Why Strings Are a Data Structure Not Just Text in DSA Python - Why It Works

Concept Flow - Why Strings Are a Data Structure Not Just Text

Input Text

↓

Store Characters in Array

↓

Access Characters by Index

↓

Perform Operations (search, slice, modify copy)

↓

Output Result

This flow shows how a string is stored as a sequence of characters, accessed by position, and used in operations like search or slicing.

Execution Sample

DSA Python

s = "hello"
print(s[1])
print(s[1:4])

This code stores a string, accesses a character by index, and slices a substring.

Execution Table

Step	Operation	String State (Array of chars)	Index Access / Slice	Output
1	Store string 'hello'	['h', 'e', 'l', 'l', 'o']	-	-
2	Access character at index 1	['h', 'e', 'l', 'l', 'o']	s[1] → 'e'	'e'
3	Slice substring from index 1 to 3	['h', 'e', 'l', 'l', 'o']	s[1:4] → ['e', 'l', 'l']	'ell'
4	End of operations	['h', 'e', 'l', 'l', 'o']	-	-

💡 All operations done, string remains unchanged as immutable data structure

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
s	undefined	'hello'	'hello'	'hello'	'hello'
output	undefined	undefined	'e'	'ell'	'ell'

Key Moments - 3 Insights

Why do we say strings are a data structure and not just plain text?

Because strings are stored as arrays of characters internally, allowing indexed access and operations like slicing, as shown in steps 1 to 3 in the execution_table.

Why can't we change a character directly in a string like s[1] = 'a'?

Strings are immutable data structures, meaning their content cannot be changed after creation. This is why in the execution_table, the string state stays the same after accessing or slicing.

How does slicing work on strings internally?

Slicing creates a new string by copying a subset of characters from the original array, as seen in step 3 where s[1:4] extracts ['e', 'l', 'l'] to form 'ell'.

Visual Quiz - 3 Questions

Look at the execution_table, what is the output when accessing s[1] at step 2?

A 'e'

B 'h'

C 'l'

D 'o'

💡 Hint

Check the 'Output' column at step 2 in the execution_table.

At which step does the slicing operation happen according to the execution_table?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look for the row where 'Slice substring' is the operation.

If strings were mutable, what would change in the variable_tracker after step 2?

A The string array would change after step 2

B The output would be undefined

C The string array would remain the same

D The output would be the whole string

💡 Hint

Refer to the 's' variable row in variable_tracker and think about immutability.

Concept Snapshot

Strings are stored as arrays of characters.
They allow indexed access and slicing.
Strings are immutable; you cannot change characters directly.
Operations create new strings, not modify existing ones.
Think of strings as a data structure, not just text.

Full Transcript

Strings are more than just text; they are stored internally as arrays of characters. This allows us to access each character by its position, called an index. For example, in the code s = "hello", the string is stored as ['h', 'e', 'l', 'l', 'o']. When we do s[1], we get 'e', the character at index 1. When we slice s[1:4], we get a new string 'ell' made from characters at positions 1, 2, and 3. Strings are immutable, meaning we cannot change a character directly. Instead, operations like slicing create new strings. This is why strings are considered a data structure, not just plain text.