# Data type extensibility and composition

**URL:** <https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827>\
**Category:** Specification\
**Created:** [May 10, 2020, 12:31pm UTC](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827 "2020-05-10T12:31:11Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![scottdixon](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/scottdixon/32/39_2.png) [@scottdixon](https://forum.opencyphal.org/u/scottdixon)\
**Post date:** [October 16, 2020, 4:15am UTC](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827/19 "2020-10-16T04:15:27Z")

</div>

> [@pavel.kirienko](#):
>
> What if we make PyDSDL emit a benign diagnostic whenever it encounters an extensible type where the extent is not defined explicitly? The diagnostic would state what the auto-deduced extent value is and how it can be provided manually.

You’re right that having to provide @extent will be a pain. I think either the tooling approach or making @sealed the default are the best options.

I’d rather make @sealed the default since this also gets rid of the default extent formula and makes naive implementations or prototyping with UAVCAN more immediate and successful. It seems like any datatype author would start with a prototype and only need to think about the future when finalizing a design. It’s in this later phase of a project that one would take the time to calculate extents properly.

---

_[View the full topic](https://forum.opencyphal.org/t/data-type-extensibility-and-composition/827)._
