You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR adopts `Span` and `RawSpan` throughout Swift Testing. Unsafe
buffer pointers and the like are replaced with spans wherever possible.
A few carve-outs:
- `Attachment`/`Attachable` are untouched for now as we need to think
through the correct API shape for them.
- Code that interacts with C functions (including code that works with C
strings) generally also must still use unsafe pointers, but the scope of
those pointers is generally constrained to some local context.
- The ABI entry point function and test content section must continue to
use unsafe pointers as they must remain broadly compatible with C.
### Checklist:
- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.
0 commit comments