[stdlib] UnsafeMutableRawPointer: load & store ~Escapable #84701
+110
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[stdlib] Unsafe[Mutable]RawPointer aligment for ~Escapable types
[stdlib] UnsafeMutableRawPointer: load[Unaligned] ~Escapable
loadUnaligned only supports loading non-BitwiseCopyable values. The generic
loadUnaligned should also be supported but it depends on UnsafePointer<T:
~Escapable>.
[stdlib] UnsafeMutableRawPointer: storeBytes of ~Escapable
Only supports non-BitwiseCopyable values. The generic storeBytes should also be
supported but it depends on UnsafePointer<T: ~Escapable>.
Test UnsafeRawPointer load of ~Escapable
Test UnsafeRawPointer store of ~Escapable
Update stability-stdlib-source-base.swift.expected for URP.load
This is necessary to allow non-Escapable values to reside in memory. Without this, it is impossible to build data types on type of Spans or other non-Escapable types.