# Move Foundation.Data in to the standard library

**URL:** <https://forums.swift.org/t/move-foundation-data-in-to-the-standard-library/15206>\
**Category:** Pitches\
**Tags:** foundation, stdlib\
**Created:** [August 13, 2018, 10:02pm UTC](https://forums.swift.org/t/move-foundation-data-in-to-the-standard-library/15206 "2018-08-13T22:02:12Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Tony\_Parker](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/tony_parker/32/273_2.png) [@Tony\_Parker](https://forums.swift.org/u/Tony_Parker)\
**Post date:** [August 14, 2018, 4:25pm UTC](https://forums.swift.org/t/move-foundation-data-in-to-the-standard-library/15206/8 "2018-08-14T16:25:58Z")

</div>

I'm looking for more concrete data about this argument of Foundation being monolithic.

One data point that we have heard is that it brings in unwanted dependencies. We intend to address this via splitting the URLSession and XML pieces out (see [Pitch: Move URLSession to new FoundationNetworking module](https://forums.swift.org/t/pitch-move-urlsession-to-new-foundationnetworking-module/14002)).

With respect to compiler optimizations, we believe those can be applied to `struct Data` regardless of its position in either the stdlib or Foundation.

Is there something else that has a measurable impact that we can address?

---

_[View the full topic](https://forums.swift.org/t/move-foundation-data-in-to-the-standard-library/15206)._