data structure
Let an agent handle data structures by type, operations, complexity and use cases.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle data structures by type, operations, complexity and use cases.
A way of organising and storing data in a computer so it can be accessed and modified efficiently, such as arrays, linked lists, trees, graphs, hash tables and semantic networks.
What it is for: Efficient storage and retrieval of data in software.
It can be choose a structure for a task; implement and test it; analyse operation complexity; serialise and persist it.
Distinguishing features
Organises data for operations
Trade-offs in time and memory
Abstract data types versus implementations
Language-independent
What it looks like
Diagrams of nodes and links, tables and code.
How it is recognised
Names such as tree, heap, hash table
Operation complexity tables
Semantic networks are knowledge structures
Related models
is a kind of - category
is used by - counterpart
is studied in - field
implements - concept
In practice
Families and kinds
linear structures: arrays, lists, stacks, queues
trees and heaps
hash tables
graphs and networks
persistent and concurrent structures
Failure modes and hazards
Wrong structure causing slow performance
Memory leaks
Concurrency bugs
Also called
+77
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Type Which structure.
Type decides operations.
Kind
Array, tree, graph.
Kind
Structure type.
- Which data structure is it? definition
- Which abstract data type does it implement? definition
Operations
Supported operations.
Operations
Operations.
- Which operations does it support? definition
- At what cost? measurement
Performance Complexity.
Complexity guides choice.
Complexity
Big O.
Complexity
Complexity.
- What are the time and space complexities? measurement
- Average or worst case? definition
Practice
Benchmarks.
Practice
Real performance.
- How does it perform on real data? measurement
- What about cache behaviour? boundary
Choice Selecting a structure.
The task decides.
Fit
Use case.
Fit
Fit for task.
- Which structure suits this access pattern? action
- What are the trade-offs? boundary
Libraries
Implementations.
Libraries
Libraries.
- Is there a well-tested library implementation? provenance
- In which language? definition
Correctness Bugs.
Structures must be correct.
Invariants
Rules.
Invariants
Invariants.
- What invariants must the structure maintain? definition
- How are they tested? provenance
Concurrency
Threads.
Concurrency
Concurrency.
- Is it safe for concurrent use? boundary
- How is access synchronised? definition
What the second pass must settle
- Should each structure be a separate entry?
- How should complexity be recorded?
- How should knowledge structures be split off?