I was in similar situation and refactored it by: 1) matching tuples 2) std::swap (for situations like collision detection) 3) make sure that "if let" is everywhere possible
-
-
-
I am doing 1 and 3 to a reasonable extent, I think my issue is more to do with the usage of the ECS library now that I think about it. the worst example is the bit which processes events. 1/2
- Još 4 druga odgovora
Novi razgovor -
-
-
the helpers on Option and Result often help keep it under control.
-
I started using expect more for options where I know I'm supposed to have something, and that helped a little bit. I'm not using results much because it's all kind of game state so there's no result passing, but I'm curious to know more about the option helpers you found useful.
- Još 1 odgovor
Novi razgovor -
-
-
Honestly, same. Having this nesting problem right now with all the rust I'm writing, and it makes it look super ugly. In other languages I aggressively avoid nesting to help readability. How fix??? (esp keeping the safety and not just unwrapping)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Been there done that
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Sounds familiar...
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I just leave a small comment after the closing bracket to show myself where it belongs to, like .... } //for } //if smth... etc.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
senior eng
previously
super mega rustlang fan (making