# data[].attributes.body
Suitable for different applications that would need to navigate forward and back. Ex. history of web pages if you need to go back or forward.

Daniel Wu

# data[].attributes.body
Has a defined beginning and end with directions pointing to Null

Sunil Dass

# data[].attributes.body
Do not have to worry about out of bounds error if implemented correctly compared to arrays.

Christian Sanchez

# data[].attributes.body
In order to identify the first element (head), it needs to be given a distinct reference, which can use more memory, and also arguably defeats the point of a circular linked list.

Harrison Vallsworth

# data[].attributes.body
since there is no distinct head or tail, circular linked lists don't have an endpoint to allow you to recognize a complete traversal.

Kenneth Huang

# data[].attributes.body
More flexible and easier to call

Truman Leung

# data[].attributes.body
Doubly linked lists require extra memory for the previous pointer, making them less memory-efficient than circular linked lists.
-Everett Murray

# data[].attributes.body
Allows for easy implementation of a queue

Christopher Lam

# data[].attributes.body
Any node can be starting point -- can traverse the list from any point
Stella Hwang

# data[].attributes.body
Allows traversing in both forward and backward directions

Ayushi Joshi

# data[].attributes.body
Doubly linked lists consume more memory.
Deleting or inserting a node requires changing two references rather than one, so there is greater runtime as well.

Jonathan Colon

# data[].attributes.body
There's more memory usage because each node now has to store a reference to the previous element in addition to the reference to the next.

# data[].attributes.body
They are harder to navigate than a traditional Array

Sunil Dass

# data[].attributes.body
Instructions: Click the + at the bottom right. Then, type in a pro or a con and include your name in your response. Click publish. Then move it to the right section.

Try to write one that hasn't been mentioned already.

Another option is to expand on something already mentioned by providing details or why you think differently.

Or write about another data structure's pro or con (review for midterm 🤓). Just specificy the data structure and if you're writing a pro or a con.

# data[].attributes.body
Cons

# data[].attributes.body
Cons

# data[].attributes.body
Pros

# data[].attributes.body
Pros

# data[].attributes.wish_content.attachment_props.question
When do you start studying for the midterm?

# data[].attributes.body
Doubly Linked Lists

# data[].attributes.body
Circular Linked Lists