@@ -63,12 +63,12 @@ Assumptions:
6363 + [ Function templates] ( #function-templates )
6464 + [ Function templates: import as Swift generic functions] ( #function-templates-import-as-swift-generic-functions )
6565 + [ Function templates: allow to specify template arguments] ( #function-templates-allow-to-specify-template-arguments )
66- + [ Function templates: calls to specific specilalizations ] ( #function-templates-calls-to-specific-specilalizations )
66+ + [ Function templates: calls to specific specializations ] ( #function-templates-calls-to-specific-specializations )
6767 + [ Function templates: calls with generic type parameters] ( #function-templates-calls-with-generic-type-parameters )
6868 + [ Function templates: importing as real generic functions] ( #function-templates-importing-as-real-generic-functions )
6969 + [ Class templates] ( #class-templates )
7070 + [ Class templates: importing instantiation behind typedef] ( #class-templates-importing-instantiation-behind-typedef )
71- + [ Class templates: importing specific specilalizations ] ( #class-templates-importing-specific-specilalizations )
71+ + [ Class templates: importing specific specializations ] ( #class-templates-importing-specific-specializations )
7272 + [ Class templates: using with generic type parameters] ( #class-templates-using-with-generic-type-parameters )
7373 + [ Class templates: using in generic code through a synthesized protocol] ( #class-templates-using-in-generic-code-through-a-synthesized-protocol )
7474 + [ Class templates: importing as real generic structs] ( #class-templates-importing-as-real-generic-structs )
@@ -1902,7 +1902,7 @@ struct Employee {
19021902 private func _getName() -> UnsafePointer<std.string>
19031903
19041904 // void setName(std::string newName);
1905- private func _setName(_ newName: std.string)
1905+ private mutating func _setName(_ newName: std.string)
19061906
19071907 // Swifty API.
19081908 public var name: std.string {
@@ -2436,7 +2436,7 @@ possible to do so when importing a C++ function template as a C++ generic
24362436function; "inout"-ness of an argument can't change across instantiations of a
24372437generic function in Swift.
24382438
2439- ### Function templates: calls to specific specilalizations
2439+ ### Function templates: calls to specific specializations
24402440
24412441From an implementation point of view, it is easy to compile Swift code that
24422442calls C++ function templates if template arguments are concrete types that are
@@ -2615,7 +2615,7 @@ struct MagicNumber {}
26152615typealias WrappedMagicNumber = __CxxTemplateInst12MagicWrapperI11MagicNumberE
26162616```
26172617
2618- ### Class templates: importing specific specilalizations
2618+ ### Class templates: importing specific specializations
26192619
26202620Just like with calls to C++ function templates, it is easy to compile a use of a
26212621C++ class templates if the usage in Swift code unambiguously specifies which
0 commit comments