Codechange: Store industry cargo data in vector instead of array. #12159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Problem
Industries store data for 16 incoming and 16 outgoing cargos. Most of the time these are empty as original specs only permitted 2 or 3 of each.
#10541 wants to extend the industry cargo history from 2 periods to 25 periods, which would make the industry data size increase quite a bit.
Description
Replace fixed accepts and produced arrays with vectors. This allows the cargo data to be sized more appropriately.
Limitations
This does not have much memory impact by itself, but is useful for #10541.
Does not rename types, so e.g.
ProducedCargoArray
is now a vector...Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.