# Add @ArrayBuilder to the standard library

**URL:** <https://forums.swift.org/t/add-arraybuilder-to-the-standard-library/83811>\
**Category:** Pitches\
**Created:** [December 22, 2025, 7:39pm UTC](https://forums.swift.org/t/add-arraybuilder-to-the-standard-library/83811 "2025-12-22T19:39:27Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![vanvoorden](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/vanvoorden/32/33619_2.png) [@vanvoorden](https://forums.swift.org/u/vanvoorden)\
**Post date:** [December 23, 2025, 6:12pm UTC](https://forums.swift.org/t/add-arraybuilder-to-the-standard-library/83811/16 "2025-12-23T18:12:40Z")

</div>

> [@cal](#):
>
> Since the enum in this case is “just a namespace” and serves no purpose at runtime, what are the technical obstacles to back deploying it, other than that this isn’t implemented yet? Naively it seems trivially back deployable if all the associated static functions are back-deployed and / or emitted into the client.

There might be some clues for you from the support to back-deploy `Span` _et al_:

> [@Supporting Span in packages](https://forums.swift.org/t/supporting-span-in-packages/81667):
>
> As we approach the release of Swift 6.2, I would like to provide some information about how to support Span in packages. As you may have noticed in the pre-released compilers, Span and its related types are being added to the standard library with backdeployment support for Darwin-based platforms. While the types are backdeployable, there is a limit to how far back they can be back-deployed, so that there are restrictions both on the compiler and on the deployment. The Span family of types incl…

---

_[View the full topic](https://forums.swift.org/t/add-arraybuilder-to-the-standard-library/83811)._