Mention module name and presence in toolchain in README#1233
Merged
stmontgomery merged 2 commits intoJul 22, 2025
Conversation
iamleeg
approved these changes
Jul 22, 2025
iamleeg
left a comment
Contributor
There was a problem hiding this comment.
Looks good: it's always best to tell people what they should do before telling them what they don't need to do.
briancroom
approved these changes
Jul 22, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This adds a mention of the testing library's module name (
import Testing) and its presence in officially-supported Swift toolchains in theREADME.Motivation:
Some users have been confused about whether they need to declare a package dependency on the
swift-testingpackage to use Swift Testing. It's included in Swift toolchains for officially-supported platforms, so we generally do not recommend declaring such a package dependency, and doing so can lead to a degraded experience with integrated tools.Checklist: