title says it all. the lack of stable urls to pages like Array.count make it hard for educational resources, API docs, and swift-aware typesetting software to reference standard library symbols.
the various sections under the symbol directory like “Adding Elements” in Array also do not have html id’s, and cannot be referred to. this means anyone writing a tutorial trying to reference a group of APIs on a standard library symbol has to direct visitors to the top of the page.
it’s a problem because tooling and Swift-specific typesetting software cannot programmatically generate links from doccomments alone. they need to make network requests to apple.com and crawl the parent pages.
I believe that number is a hash of the symbol identifier, as is typical with DocC:
Both methods have an identical symbol path of SlothCreator/Sloth/update(_:) . In this scenario, and to ensure uniqueness, DocC uses the symbol’s unique identifier instead of its name to disambiguate. Use Xcode’s code completion feature — which you can invoke by pressing the Escape key or Control-Space — when adding the symbol link to insert the correct identifier for each symbol.
The real issue is that the Swift Standard Library’s documentation isn’t hosted elsewhere. Personally, I think it should be hosted on the swift.org domain or through a GitHub page, using DocC.
Speaking of which, a permalink shouldn’t change even if the standard library did. If I want a stable link to documentation like that, I usually link to specific lines in a specific file in a specific GitHub commit.
To get started, generated documentation for the Swift-DocC project itself is hosted at swift.org/documentation. Longer-term goals include adding documentation to more packages, as well as migrating documentation for the standard library and other documentation across Swift.org. This will make it even easier for the community to participate in documenting and teaching Swift.