Some comments on the code, based on Tictactoe example (https://github.com/Microsoft/BosqueLanguage/blob/master/docs/tictactoe.md https://github.com/Microsoft/Bo

Some comments on the code, based on Tictactoe example (https://github.com/Microsoft/BosqueLanguage/blob/master/docs/tictactoe.md https://github.com/Microsoft/BosqueLanguage/blob/master/docs...): 1. overall quite nice looking and easy to understand 2. too verbose in places, e.g. this constant structure: const winPositionOptions: List[List[[Int, Int]]] = List[List[[Int, Int]]]@{ List[[Int, Int]]@{ @[ 0, 0 ], @[ 0, 1 ], @[ 0, 2 ] }, List[[Int, Int]]@{ @[ 0, 1 ], @[ 1, 1 ], @[ 2, 1 ] }, List[[Int, Int]]@{ @[ 0, 2 ], @[ 1, 2 ], @[ 2, 2 ] }, List[[Int, Int]]@{ @[ 0, 0 ], @[ 1, 0 ], @[ 2, 0 ] }, List[[Int, Int]]@{ @[ 1, 0 ], @[ 1, 1 ], @[ 1, 2 ] }, List[[Int, Int]]@{ @[ 2, 0 ], @[ 2, 1 ], @[ 2, 2 ] }, List[[Int, Int]]@{ @[ 0, 0 ], @[ 1, 1 ], @[ 2, 2 ] }, List[[Int, Int]]@{ @[ 0, 2 ], @[ 1, 1 ], @[ 2, 0 ] } }; Has types defined in 10 places, 9 of which are redundant. Also you are using @{...} for lists and @[...] for tuples; a more usual convention (in e.g. Python or Haskell) would be [...] and (...) respectively. 3. String types aren't intuitive (at least to me). E.g. in this code: const playerX: String[PlayerMark] = 'x'#PlayerMark; It appears that a String[PlayerMark] is a subset of String that can have the values 'x' or 'o'. I would have preferred something like: type PlayerMark = 'x' | 'o'; type PlayerMarkOrBlank = 'x' | 'o' | ' ';