# Proposed change to variable-length arrays

**URL:** <https://forum.opencyphal.org/t/proposed-change-to-variable-length-arrays/740>\
**Category:** Specification\
**Created:** [January 31, 2020, 4:53pm UTC](https://forum.opencyphal.org/t/proposed-change-to-variable-length-arrays/740 "2020-01-31T16:53:49Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [February 4, 2020, 2:27pm UTC](https://forum.opencyphal.org/t/proposed-change-to-variable-length-arrays/740/6 "2020-02-04T14:27:04Z")

</div>

> [@scottdixon](#):
>
> Do we add `@align` but only allow it for aligning dynamic arrays in 1.0 and expanding its role in 1.1?

Sigh. Okay. I suppose we could go with this one, but we should also allow its placement before the `@union` directive to indicate that the tag should be aligned:

```auto
@align
@union # The tag is prepended with up to 7 bits of padding.
uint8 a
float16 b

```

Later we will be able to expand its functionality as follows:

- Add an optional argument to select arbitrary alignment in bits.
- Support the case where `(_offset_ % 8).count > 1` by requiring implementations to compute the required alignment at runtime (I am worried about this runtime thing because it does complicate min/max size computation).

Is it “align” or “aligned”? I suspect “align” suits the purpose better.

Would you like to submit a PR to the spec yourself where we could then settle down the exact implementation details?

---

_[View the full topic](https://forum.opencyphal.org/t/proposed-change-to-variable-length-arrays/740)._
