@@ -906,7 +906,7 @@ printDeserialized(getSerializedFloat())
906
906
C++ container types, like the [`std::vector`](https://en.cppreference.com/w/cpp/container/vector) class
907
907
template,
908
908
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)
910
910
in Swift, as such use is not
911
911
associated with its owning container which can get destroyed
912
912
while the iterator is still in use.
@@ -920,7 +920,7 @@ conforms some C++ container types to protocols that:
920
920
These protocols and their conformance rules are described below.
921
921
The recommended approach for using C++ containers that conform to these
922
922
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).
924
924
925
925
### Some C++ Containers Are Swift Collections
926
926
@@ -986,7 +986,7 @@ will most likely make a deep copy of the container when:
986
986
987
987
This constraint is tracked on the [ status page] ( status#performance-constraints ) .
988
988
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).
990
990
991
991
#### Conformance Rules for Random Access C++ Collections
992
992
0 commit comments