Feedback: Confusing imports at interim stages of project about rust-sokoban HOT 2 CLOSED

My additions were:

• Centering the game field
• Preventing more than one box from being pushed by the player
• Making animation frame duration more easily configurable for myself

I also partially implemented differently-coloured boxes and spots before actually reading that section of the book.

from rust-sokoban.

hey @danieldeankon! thanks for the feedback!

Unused imports
I agree the imports are confusing, especially unused imports. They are there because code moved around in the starting stages of the book and code samples ended up split between multiple chapters so some of the imports were kind of left behind. I've created #79.

Compact imports
Yep, I think as a matter of style we should probably use compact imports throughout, created #80.

Explaining imports
I think this is probably the least explained part, but I kind of did this intentionally. I wanted to leave a bit for whoever is following to have to figure out themselves, add/remove imports and try to understand why they are there. I think once we remove unused imports and unify the import style hopefully this one will be better.

I found it a useful exercise to go off the book's track at various places and implement my own additions to the sokoban game

This is great! What did you implement extra? I might add a few ideas throughout the book for people to try out.

I'd like to know more about why games use ECS so often

This is a great question. I kind of glossed over this on purpose since it's a really big topic. I think you certainly don't have to use ECS, it's entirely possible to do a game using inheritance or composition. For rust games specifically, I have found ECS to be easier to work with the borrow checker.

from rust-sokoban.