# Strict Memory Safety on Windows

**URL:** <https://forums.swift.org/t/strict-memory-safety-on-windows/83699>\
**Category:** Windows\
**Created:** [December 13, 2025, 5:55pm UTC](https://forums.swift.org/t/strict-memory-safety-on-windows/83699 "2025-12-13T17:55:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![0xTim](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/0xtim/32/27968_2.png) [@0xTim](https://forums.swift.org/u/0xTim)\
**Post date:** [December 13, 2025, 5:55pm UTC](https://forums.swift.org/t/strict-memory-safety-on-windows/83699/1 "2025-12-13T17:55:37Z")

</div>

I’m working with some of the new strict memory checking APIs to write safer code when interacting with C code, such as converting some of the `UnsafeMutablePointer` APIs to use `MutableSpan`. This all works well, but looks like this hasn’t been implemented for Windows. Am I missing something or is this a missing feature?

See [Vapor Authentication 3 by 0xTim · Pull Request #73 · vapor/authentication · GitHub](https://github.com/vapor/authentication/pull/73) for the PR, with usages [here](https://github.com/vapor/authentication/pull/73/files#diff-f4181c1cda8932c4cf4b1ffb95aa864ac48049f4b656ba6720da79487af4a00fR85) and the Windows failures [here](https://github.com/vapor/authentication/actions/runs/20195476422/job/57979103728?pr=73#step:5:771)