Editing Bitboard (section)

====Cons====
Bitboard representations have much longer code, both source and object code.  Long bit-twiddling sequences are technically tricky to write and debug.  The bitboards themselves are sparse, sometimes containing only a single one bit in 64, so bitboard implementations are memory-intensive.  Both these issues may increase cache misses or cause cache thrashing.

If the processor does not have hardware instructions for 'first one' (or '[[count leading zeros]]') and '[[ONES|count ones]]' (or 'count zeros'), the implementation will be significantly handicapped, as these operations are extremely inefficient to code as assembly language loops.