BUG: Default constructor for Game
is permitted, but leads to uninitialised object
#463
Milestone
Game
is permitted, but leads to uninitialised object
#463
It's not intended to be able to call the default constructor on
Game
. However, doing so does not lead to an immediate error, but aRuntimeError
later:Although we probably want to give some further consideration to how we construct games (and indeed whether possibly we want more than one class for games, based on their representation), the simplest fix is just to disallow this with a suitable exception.
This should be fixed in
maint16_1
first and merged forward.The text was updated successfully, but these errors were encountered: