Code cleanup: replace iterator loops with range-based for-loops
Bug #1377642 reported by
GunChleoc
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| widelands |
Won't Fix
|
Low
|
GunChleoc | ||
Bug Description
Where there is no direct iterator manipulation, replace iterator loops with range based for loops.
This will save us lines in the code and make things more readable.
Related branches
Revision history for this message
| SirVer (sirver) wrote | #1 |
| Changed in widelands: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in widelands: | |
| assignee: | nobody → GunChleoc (gunchleoc) |
| milestone: | none → build20-rc1 |
| status: | Confirmed → In Progress |
| Changed in widelands: | |
| milestone: | build20-rc1 → build21-rc1 |
| summary: |
- Code cleanup: replace iterator loops with range based for loops + Code cleanup: replace iterator loops with range-based for-loops |
Revision history for this message
| GunChleoc (gunchleoc) wrote | #2 |
| Changed in widelands: | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
+1. But I think there should not be very many of those in the code based. For these use cases we used to have container_iterate which we replaced through range based loops already.