Question about the choice of padding fields

I noticed that FlatBuffers generates padding for c/cpp as individual fields, e.g.:

uint8_t padding0__;
uint8_t padding1__;
uint8_t padding2__;

instead of a single array:

uint8_t padding__[3];

I understand why FlatBuffers generates explicit padding and manually controls struct layout, but I couldn't find any documentation explaining the choice of individual padding fields versus arrays.

Was this a deliberate design decision? If so, what were the motivations?

The issue identifies generated C/C++ padding fields but names no source file or test. Review the code-generation output and existing documentation to determine whether the individual-field choice has a documented rationale; done means adding a clear explanation if the project confirms one.

Written by the indexing model from the issue text.