Talk:Computer Go/Writing a Go Engine

Notes for further expansion:
 * Obtaining Legal Play
 * Representing the board
 * Chain tracking
 * Liberty counting
 * Suicides and Captures
 * Ko tracking
 * Data Structures and Algorithms
 * Fundamental Decisions
 * Pattern matching (why, when, and how)
 * Tables, data files, etc vs. hard-coded rules
 * Learning
 * Regression testing
 * Storing coordinate based information
 * Representing the board
 * 1D vs 2D?
 * Array of structures or multiple arrays?
 * Collections of points
 * Speed vs. Size trade-offs
 * sets, hashes, unique lists, and other
 * Spatial representations
 * Surrounding chains/groups
 * Distance from edge
 * Next stone in 4 cardinal directions
 * Incremental updates verses recalculation ???
 * Caching methodologies ???
 * Implementing Go Concepts
 * Life and Death
 * Territory and Influence
 * Libraries of Joseki and Fuseki
 * Chain and Liberty tracking
 * Array of chain ID's
 * Liberty accuracy requirements
 * 4 liberties for tactial stability ???
 * Extend to 5 liberties in contact fights ???
 * Incremental approaches verses recalculation
 * Tactical Reading
 * Minimax vs. AlphaBeta vs. Lambda ???
 * Group Tracking ???
 * Full Board Evaluators ???