# \[Accepted\] SE-0349: Unaligned loads and stores from raw memory

**URL:** <https://forums.swift.org/t/accepted-se-0349-unaligned-loads-and-stores-from-raw-memory/56748>\
**Category:** Announcements\
**Tags:** pointers\
**Created:** [April 14, 2022, 2:33am UTC](https://forums.swift.org/t/accepted-se-0349-unaligned-loads-and-stores-from-raw-memory/56748 "2022-04-14T02:33:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_McCall](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/john_mccall/32/1351_2.png) [@John\_McCall](https://forums.swift.org/u/John_McCall)\
**Post date:** [April 14, 2022, 2:33am UTC](https://forums.swift.org/t/accepted-se-0349-unaligned-loads-and-stores-from-raw-memory/56748/1 "2022-04-14T02:33:11Z")

</div>

Hello, Swift community.

The [review](https://forums.swift.org/t/se-0349-unaligned-loads-and-stores-from-raw-memory/56423) of [SE-0349](https://github.com/apple/swift-evolution/blob/main/proposals/0349-unaligned-loads-and-stores.md) ended on April 12th. Feedback was quite light, but what was there was positive; a common theme was that this feature is long overdue. The Core Team agrees, and SE-0349 is therefore **approved**. While it would be nice if the precondition on these operations (that the underlying type is trivially copyable) could be made a static constraint in the type system, the Core Team is unwilling to hold the proposal up until that is possible to express.

I'd like to thank the members of the community who participated in the pitch and review of this proposal. Changes like these are individually minor, but taken together, they can have an outsized impact on the quality of life of programmers who regularly run into the situations considered here.

John McCall  
Review Manager