对元素持有弱引用的Swift数组 #1692

zhangqicode · 2017-05-24T04:36:10Z

@sqrthree，翻译完成

issue 1679

update

ZhangRuixiang · 2017-05-24T07:38:48Z

@sqrthree 认领校对

Danny1451 · 2017-05-24T09:53:12Z

@sqrthree 申请校对之前一直比较忙

linhe0x0 · 2017-05-25T02:53:32Z

@ZhangRuixiang @Danny1451 妥妥哒

ZhangRuixiang · 2017-05-25T16:24:43Z

TODO/swift-arrays-holding-elements-weak-references.md

@@ -1,26 +1,26 @@
 > * 原文地址：[Swift Arrays Holding Elements With Weak References](https://marcosantadev.com/swift-arrays-holding-elements-weak-references/)
 > * 原文作者：[Marco Santarossa](https://marcosantadev.com/about-me/)
 > * 译文出自：[掘金翻译计划](https://github.com/xitu/gold-miner)
-> * 译者：
+> * 译者：[zhangqippp](https://github.com/zhangqippp)
 > * 校对者：


ZhangRuixiang

ZhangRuixiang · 2017-05-25T16:33:40Z

TODO/swift-arrays-holding-elements-weak-references.md


-For “not type-safe”, I mean that the compiler is not able to infer the type of the objects inside `NSPointerArray`, since it uses pointers of objects `AnyObject`. For this reason, when you get an object from the array, you must cast it to your object type:
+“非类型安全”，在此处的意思是编译器无法隐含 `NSPointerArray` 内部对象的类型，因为它使用的是 `AnyObject` 型对象的指针。因此，当你从数组中获取一个对象时，你需要检查它是否是你所需要的类型：


无法隐含 NSPointerArray 内部对象的类型 => 无法推断隐含在NSPointerArray 内部的对象的类型

获取一个对象时 => 获取对象时

when you get an object from the array, you must cast it to your object type:
cast 是要把 array 里面的 AnyObject 转成你要的 type 吧

因此，当你从数组中获取一个对象时，你需要把它转成你所需要的类型：

ZhangRuixiang · 2017-05-25T16:37:46Z

TODO/swift-arrays-holding-elements-weak-references.md


-A possible workaround is creating a new class `WeakRef` with a generic weak property `value`:
+一个可行的方案是创建一个新类 `WeakRef` ，它带有一个普通的weak属性 `value`：

 ```
 classWeakRef<T>whereT: AnyObject{


classWeakRef => class WeakRef

ZhangRuixiang · 2017-05-25T16:41:44Z

TODO/swift-arrays-holding-elements-weak-references.md


-For “not type-safe”, I mean that the compiler is not able to infer the type of the objects inside `NSPointerArray`, since it uses pointers of objects `AnyObject`. For this reason, when you get an object from the array, you must cast it to your object type:
+“非类型安全”，在此处的意思是编译器无法隐含 `NSPointerArray` 内部对象的类型，因为它使用的是 `AnyObject` 型对象的指针。因此，当你从数组中获取一个对象时，你需要检查它是否是你所需要的类型：

 ```
 ifletfirstObject=array.object(at:0)as?MyClass{// Cast to MyClass


ifletfirstObject => if let firstObject
这一行代码格式不对，同时请检查一下其余代码块的格式

ZhangRuixiang · 2017-05-25T16:42:42Z

TODO/swift-arrays-holding-elements-weak-references.md


-If you want to clean the array removing the objects with value `nil`, you can write the following method:
+如果你想清理数组，去除其中值为 `nil` 的对象，你可以使用下面的方法：

 ```
 funccompact(){


funccompact => func compact

ZhangRuixiang

@zhangqippp @sqrthree 校对完成，zhangqippp翻译的非常棒，校对不足之处，请多多指教~

Danny1451

校对完毕，翻译的不错，很用心。

Danny1451 · 2017-05-26T02:03:32Z

TODO/swift-arrays-holding-elements-weak-references.md


 ![](https://marcosantadev.com/wp-content/uploads/header-1.jpg)

-In iOS development there are moments where you ask yourself: “To weak, or not to weak, that is the question”. Let’s see how “to weak” with the arrays.
+在 iOS 开发中我们经常面临一个问题：“使用弱引用，还是不使用弱引用？”。我们来看一下如何在数组中使用弱引用。


To weak, or not to weak, that is the question 这是在模仿莎士比亚的哈姆雷特的经典台词，建议可以参照台词的翻译效果意译。

在 iOS 开发中我们经常面临一个问题：“用弱引用还是不用，这是一个问题。”。我们来看一下如何在数组中使用弱引用。

其实我本来想翻译成：“那么问题来了，用弱引用还是不用”😂

To be or not to be, that is the question. 原译为"生存还是毁灭，这是一个问题。"

这边其实我也没想出特别好的 😂

Danny1451 · 2017-05-26T02:03:44Z

TODO/swift-arrays-holding-elements-weak-references.md


-*In this article, I speak about memory management without explaining it since it would be beyond the goal of this article. The [official documentation](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html) is a good starting point to learn this subject. Then, if you have other doubts, please leave a comment and I’ll reply as soon as possible.*
+*在本文中，我会谈到内存管理但是不会解释它，因为这不是本文的主题。  这里的[官方文档](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html)可以帮助你开始学习内存管理。 如果你有其它疑问，请留言，我会尽快给予回复。*


这里的[官方文档]可以帮助你开始学习内存管理。
the 可以不用翻译

[官方文档]是学习内存管理的一个好的起点。

Danny1451 · 2017-05-26T02:05:02Z

TODO/swift-arrays-holding-elements-weak-references.md


-`Array` is the most popular collection in Swift. By default, it maintains a strong references of its elements. Even if this behaviour is useful most of the time, you might have some scenarios where you would want to use weak references. For this reason, Apple provides an alternative to `Array` which maintains weak references of its elements: **NSPointerArray**.
+`Array` 是Swift中使用最多的集合。它会默认的对其元素持有强引用。 这种默认的行为在大多数时候都很有用，但是在某些场景下你可能想要使用弱引用。因此，苹果公司给我们提供了一个 `Array` 的替代品：**NSPointerArray**，这个类对它的元素持有弱引用。


它会默认的对其元素持有强引用。

默认地

Danny1451 · 2017-05-26T02:12:41Z

TODO/swift-arrays-holding-elements-weak-references.md


 ```
 protocolMyProtocol: class{}
 ```

-2. If you want to play with `NSPointerArray`, I suggest you to avoid the Playground since you may have odd behaviours with the retain count. A sample app would be better.
+2. 如果你想试用一下 `NSPointerArray`，我建议不要试用 Playground ，因为你可能因为引用计数问题得到一些奇怪的行为。使用一个简单的 app 会更好。


试用

使用

Danny1451 · 2017-05-26T02:16:41Z

TODO/swift-arrays-holding-elements-weak-references.md


-For “not type-safe”, I mean that the compiler is not able to infer the type of the objects inside `NSPointerArray`, since it uses pointers of objects `AnyObject`. For this reason, when you get an object from the array, you must cast it to your object type:
+“非类型安全”，在此处的意思是编译器无法隐含 `NSPointerArray` 内部对象的类型，因为它使用的是 `AnyObject` 型对象的指针。因此，当你从数组中获取一个对象时，你需要检查它是否是你所需要的类型：


when you get an object from the array, you must cast it to your object type:
cast 是要把 array 里面的 AnyObject 转成你要的 type 吧

因此，当你从数组中获取一个对象时，你需要把它转成你所需要的类型：

Danny1451 · 2017-05-26T02:24:42Z

TODO/swift-arrays-holding-elements-weak-references.md


-I guess you are not going to use arrays with weak references very often, but it’s not an excuse not to know how to achieve it. In iOS development the memory management is very important to avoid memory leaks, since iOS doesn’t have a garbage collector. ¯\_(ツ)_/¯
+你可能不会经常使用持有弱引用的数组，但是你仍然可以学习如何实现它。在 iOS 开发中，内存管理是非常重要的，我们应该避免内存泄露，因为 iOS 没有垃圾回收器。 ¯\_(ツ)_/¯


你可能不会经常使用持有弱引用的数组，但是你仍然可以学习如何实现它。

你可能不会经常使用持有弱引用的数组，但是这不是不去了解其实现原理的理由。

Danny1451 · 2017-05-26T02:27:29Z

@zhangqippp @sqrthree 校对完成

zhangqicode · 2017-05-26T03:04:52Z

@ZhangRuixiang , @Danny1451 , @sqrthree , 根据校对意见修改完毕

linhe0x0

很棒，但是有一个小问题还望辛苦修改下哈。文中有多处用斜体了，请参考 wiki 斜体文字使用加粗样式代替

zhangqicode · 2017-05-26T03:33:39Z

@sqrthree , 斜体修改完毕

linhe0x0 · 2017-05-26T03:34:29Z

@zhangqippp 已经 merge 啦~ 快快麻溜发布到掘金专栏然后给我发下链接，方便及时添加积分哟。

zhangqicode added 2 commits May 23, 2017 11:40

Merge pull request #1 from xitu/master

9728a4d

update

初译完成

0c4ee93

linhe0x0 added iOS 校对认领 labels May 24, 2017

linhe0x0 mentioned this pull request May 24, 2017

对元素持有弱引用的Swift数组 #1679

Closed

linhe0x0 added 正在校对 and removed 校对认领 labels May 25, 2017

ZhangRuixiang reviewed May 25, 2017

View reviewed changes

Danny1451 reviewed May 26, 2017

View reviewed changes

根据校对意见修改

273dc6e

linhe0x0 requested changes May 26, 2017

View reviewed changes

将斜体修改为加粗

b808e92

linhe0x0 approved these changes May 26, 2017

View reviewed changes

linhe0x0 merged commit e2e5fc0 into xitu:master May 26, 2017

linhe0x0 added 翻译完成 and removed 正在校对 labels May 26, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

对元素持有弱引用的Swift数组 #1692

对元素持有弱引用的Swift数组 #1692

zhangqicode commented May 24, 2017

ZhangRuixiang commented May 24, 2017

Danny1451 commented May 24, 2017

linhe0x0 commented May 25, 2017

ZhangRuixiang May 25, 2017

ZhangRuixiang May 25, 2017 •

edited

Loading

Danny1451 May 26, 2017

ZhangRuixiang May 25, 2017

ZhangRuixiang May 25, 2017

ZhangRuixiang May 25, 2017

ZhangRuixiang left a comment •

edited

Loading

Danny1451 left a comment

Danny1451 May 26, 2017

zhangqicode May 26, 2017

Danny1451 May 26, 2017

Danny1451 May 26, 2017

Danny1451 May 26, 2017

Danny1451 May 26, 2017

Danny1451 May 26, 2017

Danny1451 May 26, 2017

Danny1451 commented May 26, 2017

zhangqicode commented May 26, 2017

linhe0x0 left a comment

zhangqicode commented May 26, 2017

linhe0x0 commented May 26, 2017


		For “not type-safe”, I mean that the compiler is not able to infer the type of the objects inside `NSPointerArray`, since it uses pointers of objects `AnyObject`. For this reason, when you get an object from the array, you must cast it to your object type:
		“非类型安全”，在此处的意思是编译器无法隐含 `NSPointerArray` 内部对象的类型，因为它使用的是 `AnyObject` 型对象的指针。因此，当你从数组中获取一个对象时，你需要检查它是否是你所需要的类型：


		In this article, I speak about memory management without explaining it since it would be beyond the goal of this article. The [official documentation](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html) is a good starting point to learn this subject. Then, if you have other doubts, please leave a comment and I’ll reply as soon as possible.
		在本文中，我会谈到内存管理但是不会解释它，因为这不是本文的主题。这里的[官方文档](https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/AutomaticReferenceCounting.html)可以帮助你开始学习内存管理。如果你有其它疑问，请留言，我会尽快给予回复。


		`Array` is the most popular collection in Swift. By default, it maintains a strong references of its elements. Even if this behaviour is useful most of the time, you might have some scenarios where you would want to use weak references. For this reason, Apple provides an alternative to `Array` which maintains weak references of its elements: NSPointerArray.
		`Array` 是Swift中使用最多的集合。它会默认的对其元素持有强引用。这种默认的行为在大多数时候都很有用，但是在某些场景下你可能想要使用弱引用。因此，苹果公司给我们提供了一个 `Array` 的替代品：NSPointerArray，这个类对它的元素持有弱引用。


		I guess you are not going to use arrays with weak references very often, but it’s not an excuse not to know how to achieve it. In iOS development the memory management is very important to avoid memory leaks, since iOS doesn’t have a garbage collector. ¯\_(ツ)_/¯
		你可能不会经常使用持有弱引用的数组，但是你仍然可以学习如何实现它。在 iOS 开发中，内存管理是非常重要的，我们应该避免内存泄露，因为 iOS 没有垃圾回收器。 ¯\_(ツ)_/¯

对元素持有弱引用的Swift数组 #1692

对元素持有弱引用的Swift数组 #1692

Conversation

zhangqicode commented May 24, 2017

ZhangRuixiang commented May 24, 2017

Danny1451 commented May 24, 2017

linhe0x0 commented May 25, 2017

Choose a reason for hiding this comment

ZhangRuixiang May 25, 2017 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ZhangRuixiang left a comment • edited Loading

Choose a reason for hiding this comment

Danny1451 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Danny1451 commented May 26, 2017

zhangqicode commented May 26, 2017

linhe0x0 left a comment

Choose a reason for hiding this comment

zhangqicode commented May 26, 2017

linhe0x0 commented May 26, 2017

ZhangRuixiang May 25, 2017 •

edited

Loading

ZhangRuixiang left a comment •

edited

Loading