Skip to content

Commit b210d6c

Browse files
authored
Fix bad links (#366)
1 parent f46a0f6 commit b210d6c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

documentation/cxx-interop/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -906,7 +906,7 @@ printDeserialized(getSerializedFloat())
906906
C++ container types, like the [`std::vector`](https://en.cppreference.com/w/cpp/container/vector) class
907907
template,
908908
typically provide iterator-based APIs for users in C++.
909-
Using a C++ iterator is [unsafe](index#do-not-use-c-iterators-in-swift)
909+
Using a C++ iterator is [unsafe](#do-not-use-c-iterators-in-swift)
910910
in Swift, as such use is not
911911
associated with its owning container which can get destroyed
912912
while the iterator is still in use.
@@ -920,7 +920,7 @@ conforms some C++ container types to protocols that:
920920
These protocols and their conformance rules are described below.
921921
The recommended approach for using C++ containers that conform to these
922922
protocols is summarized in a
923-
[follow-up section](index#recommended-approach-for-using-c-containers).
923+
[follow-up section](#recommended-approach-for-using-c-containers).
924924
925925
### Some C++ Containers Are Swift Collections
926926
@@ -986,7 +986,7 @@ will most likely make a deep copy of the container when:
986986

987987
This constraint is tracked on the [status page](status#performance-constraints).
988988
Several strategies for working around this constraint are
989-
[presented below](index#using-c-containers-in-performance-sensitive-swift-code).
989+
[presented below](#using-c-containers-in-performance-sensitive-swift-code).
990990

991991
#### Conformance Rules for Random Access C++ Collections
992992

0 commit comments

Comments
 (0)