Skip to content

Commit 7a53b2f

Browse files
committed
Stack code added
1 parent 40920db commit 7a53b2f

File tree

4 files changed

+70
-0
lines changed

4 files changed

+70
-0
lines changed

Data Structure/Stack/README.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Stack
2+
3+
A **stack** is an Abstract Data Type (ADT), commonly used in most programming languages. It is named stack as it behaves like a real-world stack, for example – a deck of cards or a pile of plates, etc.
4+
5+
A real-world stack allows operations at one end only. For example, we can place or remove a card or plate from the top of the stack only. Likewise, Stack ADT allows all data operations at one end only. At any given time, we can only access the top element of a stack.
6+
7+
This feature makes it LIFO data structure. LIFO stands for Last-in-first-out. Here, the element which is placed (inserted or added) last, is accessed first. In stack terminology, insertion operation is called PUSH operation and removal operation is called POP operation.
8+
9+
10+
Conceptually, a stack is simple: a data structure that allows adding and removing elements in a particular order. Every time an element is added, it goes on the top of the stack; the only element that can be removed is the element that was at the top of the stack. Consequently, a stack is said to have "first in last out" behavior (or "last in, first out"). The first item added to a stack will be the last item removed from a stack.
11+
12+
![Stack](stack.svg)
13+
14+
**Basic Operations:**
15+
16+
Stack operations may involve initializing the stack, using it and then de-initializing it. Apart from these basic stuffs, a stack is used for the following two primary operations −
17+
18+
- **push()** − Pushing (storing) an element on the stack.
19+
- **pop()** − Removing (accessing) an element from the stack.
20+
21+
To use a stack efficiently, we need to check the status of stack as well. For the same purpose, the following functionality are available too −
22+
23+
- **peek()** − get the top data element of the stack, without removing it.
24+
- **isEmpty()** − check if stack is empty.
25+
26+
27+
#### Complexity Analysis
28+
- Insertion - O(1)
29+
- Deletion - O(1)
30+
- Access - O(n)
31+
- Search - O(n)
32+
33+
34+
### More on this topic
35+
- https://en.wikipedia.org/wiki/Stack_(abstract_data_type)
36+
- https://www.tutorialspoint.com/data_structures_algorithms/stack_algorithm.htm
37+
- https://en.wikibooks.org/wiki/Data_Structures/Stacks_and_Queues

Data Structure/Stack/stack.py

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
""" Stack implementation using Python List """
2+
3+
class Stack(object):
4+
5+
def __init__(self):
6+
self.items = []
7+
8+
def isEmpty(self):
9+
return (self.items == [])
10+
11+
def push(self, item):
12+
self.items.append(item)
13+
14+
def peek(self):
15+
return self.items[len(self.items) - 1]
16+
17+
def pop(self):
18+
if self.isEmpty():
19+
return None
20+
return self.items.pop()

Data Structure/Stack/stack.svg

4.24 KB
Loading

Data Structure/Stack/test.py

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
from stack import Stack
2+
3+
stack = Stack()
4+
5+
stack.push(10)
6+
stack.push(15)
7+
8+
print(stack.isEmpty())
9+
print(stack.peek())
10+
print(stack.pop())
11+
print(stack.pop())
12+
print(stack.pop())
13+
print(stack.isEmpty())

0 commit comments

Comments
 (0)