Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.

New answers tagged

2

I see some things that may help you improve your code. Don't leak memory I see that there are a number of places in which new is invoked but there is no corresponding delete. For example, one leak can be addressed by adding this destructor: Minefield::~Minefield() { delete mCellInputHandler; } Put friend declarations in public section It's ...


1

Nice, well-presented code, apart from some spacing inconsistency following for, if etc. I think the Cell constructor should be explicit. It's odd that it's missing initializers for the timers (I use gcc -Weffc++, so tend to include them even for types that won't end up uninitialized). constexpr auto intervall = 50; would be better named interval. ...


Top 50 recent answers are included