Hi,
What’s the difference between
and
Thank you
The Swift standard library defines a base layer of functionality for writing Swift programs. Documentation for the standard library is presently hosted on the Apple Developer website.
The Swift standard library, along with its tests and inline documentation, are a part of the main Swift repository.
The Swift Programming Language is the authoritative reference for Swift, offering a guided tour, a comprehensive guide, and a formal reference of the language.
- The Swift Programming Language Book | Language reference | Swift.org
To illustrate the difference you can look at these two which discuss strings
2 Likes
The Apple docs just provide a quick summary of what Swift is and then link to Swift.org, don't really understand where the confusion comes from. As @MinerMinerMain mentioned, the standard library documentation is hosted on the Apple developer website, but you won't find, for example, an overview of Swift's concurrency model here, albeit, in my opinion, the language documentation on Swift.org is currently severely lacking. As an example, to get an understanding about the execution semantics of asynchronous functions, you actually have to find this very specific API documentation here or read the corresponding Swift Evolution proposal.
1 Like
The documentation hosted at Featured | Apple Developer Documentation is the hosted location for Apple's developer documentation, which includes documentation for the Swift open source project.
The documentation hosted on Swift.org (most of it hosted through as Jekyll articles or as DocC archives published at swift.org or docs.swift.org) has grown organically. Multiple of the workgroups have been pushing to have improved documentation, and earlier in 2025 I started an effort to formally pull it together and provide some organization and common content. There is work ongoing currently to bring the Swift Standard Library to be hosted with the other documentation on swift.org, as well as re-organize the content slightly for consistency, building on the structure that we have today for language reference guide at The Swift Programming Language.
If you're curious about the proposal, it's available at swift-org-website/_info-architecture/0003-swift-docs-proposal.md at main · swiftlang/swift-org-website · GitHub, and it being carefully coordinated with the schedules and availability of the Website Workgroup, the Documentation Tooling workgroup, and the team that manages the public infrastructure for Swift.org.
We still have some pieces to sort out - in particular the URI layout for the publishing of multiple DocC archives, and how to visually align and interconnect any hosted documentation with the current Swift.org redesign, which has been progressing since WWDC of 2025. To a large extent, I stepped into that work after it started and have been working to align this update to fit well within that project's scheduled and expected efforts.
I expect we'll resume working on after the holiday break, and as establish the structure and start to shift into migrating content. I'll be coordinating that work through GitHub issues, currently hosted on the swift-org-website repository, although I hope to have a dedicated docs repository to host issues and track the work of migrating existing content as we go.
You can see some of the initial porting work at #1201, which is coordinating updating content with the Swift Server Workgroup and Ecosystem Steering group.
In general, I've been carefully wrangling issues related to general documentation with the documentation tag in that repo.
(My hope is that we'll get the new repository established, migrate the issues related to general documentation vs. the Swift.org website to the new dedicated repository, and build up from there). The repository is expected consolidate and host a variety of content, as well as the scripts to support the static hosting with swift.org, formalizing how we're hosting to the subdomain "docs.swift.org".
That's a big answer for a comparatively short question, but hopefully shares both the original answer and provides some insight into how we're expecting that answer to change in the coming year. I completely agree that the documentation story could be notably better for Swift, and I'm actively working to enable that.
If you (or anyone, really) is interested in helping with new content, migration, or updating existing content, please reach out - there's a number of folks, both in Apple and within the broader community, that I'm coordinating with for improving specific topic areas.
10 Likes
Hi @FahadBuilds,
The first link you posted is to Apple's distribution of the documentation for the Swift standard library, which is implicitly imported and available for all Swift code, as evidenced by the main heading "Framework > Swift." As @MinerMinerMain points out, the standard library provides some basic functions and types which are broadly useful for writing code in Swift.
Since the name of that module is Swift, it seems that Apple has considered the page to be a logical place additionally to include a very quick introduction to the Swift programming language as a whole, links to documentation for other modules that are distributed with Swift and always available (such as the concurrency and regex modules), and links to some other topics related to Swift programming and Objective-C interop.
Note that Apple's distribution of the standard library documentation will include extensions to Swift standard library types that aren't available on non-Apple platforms.
The second link you posted is to The Swift Programming Language, which is a book that tries to give a (fairly) complete overview of the language. As the language continues to evolve, there's bits and pieces that are not as up-to-date as is ideal, but a lot of effort goes to keeping it actively maintained.
The book used to be hosted on Apple's website too, but (as others have described) it's now hosted on swift.org as part of organizational efforts to make the open-source documentation for the open-source language hosted on the open-source project's website.
However, I suspect the reason you're asking the question doesn't actually have to do with the infrastructure of the open-source project and ongoing efforts related to documentation, but rather asking for pointers about where to start learning a (very cool, in my opinion) programming language. So here's a good thing to know: since the standard library is integral to the language, it's not necessary to figure out the difference in order to get started with Swift.
There are many resources other than the official documentation which may be more suited to learning, but if you're looking for a first-party starting point, I'd recommend reading (parts of) The Swift Programming Language. You can always consult the standard library documentation for details of particular types and functions as needed, but it's not really meant to be read cover to cover (indeed, it's not a book, so there's not even a metaphorical cover, and no matter where the standard library documentation is hosted in future, I suspect that won't change).
2 Likes
Thank you. Actually the reason I asked is a bit of a long story
I first wanted to learn how to search docs.swift.org but I realized I couldn’t. (Related: How to search the online Swift documentation? , How is the 'search' feature of the generated documentation sites supposed to work? )
So I ended up adding this google search to my bookmarks whenever I wanted to search how to do something in swift “site:docs.swift.org/swift-book” which works for some swift code like guard (which is explained here Documentation ) but one day I wanted to search how reduce function works so I tried my little bookmark trick but didn’t find a link that explained how it worked, so I opted for a regular google search which brought me to the apple documentation, which I was confused by because reduce is a swift function not a swiftui function so I thought I’ll find it in swift.org which is I why I posted here.
1 Like
A few days ago I started a discussion with @Joseph_Heck , mirroring similar thoughts; while still in its infancy, one of his suggestions was setting up a Webex for anyone interested in contributing, brainstorming, etc. If you or anyone finds interest in this idea, let us know!
There are a lot of plans, proposals, and work happening, but the lack of manpower is a real barrier currently. If you are interested in helping, don’t hesitate reaching out to @Joseph_Heck .
P.S. if you don't mind, I have a question for you and anybody who wants to share their learning experience.
- What official documentation did you consult, if any? (Swift.org, Apple developer website, WWDC videos, Swift Evolution proposals)
- How accessible did you find these resources?
- Were you ever overwhelmed by the language and/or terms used by said resources?
1 Like
Thanks for the thorough reply. From reading your response, I get the understanding that Swift failed to distinguish itself as independent of Apple's closed-source software? Have you checked out the Swift Evolution Proposals already? As they are the most formal part of Swift's documentation, including motivation sections, future-direction sections and general implementation details. As for the accessibility issue, I would formalize the issue and potential ideas and provide it as feedback (separate post with the site-feedback tag), perhaps mirroring it in your message to @Joseph_Heck .
1 Like