vault backup: 2024-10-01 13:34:47
This commit is contained in:
@@ -18,11 +18,16 @@ Why does each Cell need to know its neighbor count? They need to show a number,
|
|||||||
|
|
||||||
Speaks English _very_ well.
|
Speaks English _very_ well.
|
||||||
|
|
||||||
|
Found a bug he wrote in column and row check before executing program by thinking about it logically and visualizing the board.
|
||||||
|
|
||||||
|
Has a bug using `.Length` of a multi-dimensional array! Will be x * y and not x as he's hoping.
|
||||||
|
|
||||||
Questions:
|
Questions:
|
||||||
1. Can you GridSize everywhere to avoid errors?
|
1. Can you GridSize everywhere to avoid errors?
|
||||||
2. Does each Cell really need to know it's neighbor mine count? Or is that something the board knows about?
|
2. Does each Cell really need to know it's neighbor mine count? Or is that something the board knows about?
|
||||||
3. Instead of a `(Row, Column)` comment, is there another way we could label the values?
|
3. Instead of a `(Row, Column)` comment, is there another way we could label the values?
|
||||||
4. Is there a way to calculate the coordinates of the surrounding cells without statically constructing a list of offset pairs?
|
4. Is there a way to calculate the coordinates of the surrounding cells without statically constructing a list of offset pairs?
|
||||||
|
5.
|
||||||
|
|
||||||
Nits:
|
Nits:
|
||||||
1. Property, field and variable naming not consistent
|
1. Property, field and variable naming not consistent
|
||||||
|
|||||||
Reference in New Issue
Block a user