Fix Linux cellular step initializer warning
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (checks) (push) Failing after 3m53s
Foundation / checks (client) (push) Failing after 4m26s
Foundation / checks (tsan) (push) Failing after 34s
Foundation / checks (network) (push) Failing after 3m7s
Foundation / checks (postgres) (push) Failing after 1m47s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-11 02:45:49 -04:00
parent 84efa4bf14
commit 127c8e795a
2 changed files with 6 additions and 1 deletions
+5
View File
@@ -6680,3 +6680,8 @@ passed.
`cmake --build build/debug --target evo-mutation-tests` regenerated successfully
but stalled before target compilation, at the same Ninja glob recheck seen above.
The direct focused MSVC executable is local evidence only; full CI is pending.
The first CI run (240) also exposed a GCC `-Werror=missing-field-initializers`
diagnostic in the pre-existing `CellularRegionStepCandidate` aggregate setup.
The initializer now explicitly supplies empty starved and heat fields; CI for
that correction is pending.
+1 -1
View File
@@ -26,7 +26,7 @@ propose_cellular_region_step(std::uint64_t begin_tick, CellularArea area,
if (ordered[i - 1]->life_id == ordered[i]->life_id)
return std::unexpected{CellularRegionStepError::duplicate_life_id};
CellularRegionStepCandidate candidate{begin_tick, begin_tick + 1, {}, {}};
CellularRegionStepCandidate candidate{begin_tick, begin_tick + 1, {}, {}, {}, {}};
candidate.lives.reserve(ordered.size());
candidate.starved.reserve(ordered.size());
std::vector<accounting::Inventory> patch_stock;