当设计模式遇上 Kotlin #1780

boileryao · 2017-06-19T03:45:53Z

Gang of Four Patterns in Kotlin, 设计模式遇上 Kotlin

翻译完成

windmxf · 2017-06-19T12:35:01Z

校对认领 @sqrthree

linhe0x0 · 2017-06-19T14:17:31Z

@windmxf 好哒

windmxf

@sqrthree 校对完成。译者翻译的很赞~~

windmxf · 2017-06-19T14:48:42Z

TODO/gang-of-four-patterns-in-kotlin.md


-It's also important to note that these patterns where discovered to overcome the shortcomings of how imperative programming languages were designed in the 90s (C++ in particular). Many modern languages provide features to overcome these issues without writing extra code or falling back to patterns.
+认识到这些模式的发明是为了弥补起源于上世纪九十年代的一些命令式编程语言（尤其是 C++）的不足是很重要的。很多现代编程语言提供了解决这些不足的特性，我们完全不需要再写多余的代码或者做刻意模仿设计模式这种事了。


[It's also important to note that these patterns]=>[需要特别说明一下，这些设计模式的发明]

windmxf · 2017-06-19T14:51:12Z

TODO/gang-of-four-patterns-in-kotlin.md


-Inspired by Mario Fusco's [Talk](https://www.youtube.com/watch?v=Rmer37g9AZM)/[Blog posts](https://www.voxxed.com/blog/2016/04/gang-four-patterns-functional-light-part-1/)/[Repository](https://github.com/mariofusco/from-gof-to-lambda) "From GoF to lambda", I decided to implement some of the most famous design patterns in computer science in Kotlin!


[I decided to implement some of the most famous design patterns in computer science in Kotlin!]=>[我决定用 Kotlin来实现一些计算机科学领域最著名的设计模式！]
可斟酌..

windmxf · 2017-06-19T14:54:08Z

TODO/gang-of-four-patterns-in-kotlin.md


-That's why —just like Mario in the `g ∘ f` repository— I will try to find a simpler, easier or more idiomatic way to solve the same problem each pattern is solving.


[a simpler, easier or more idiomatic way]=>[一种更简单方便、更惯用的方式]

windmxf · 2017-06-19T14:56:15Z

TODO/gang-of-four-patterns-in-kotlin.md


-If you don't like reading explanations, you can directly jump to my [github repository](https://github.com/lmller/gof-in-kotlin)


[reading explanations]=>[看说明文字]

windmxf · 2017-06-19T14:57:47Z

TODO/gang-of-four-patterns-in-kotlin.md


-First up are the structural patterns. This is tough, because structural patterns are about - structure! How could I implement a structure with a *different* structure? I can't. An exception is the **Decorator**. While it's technically just about structure, its usage is more about behavior or responsibilities.


[I can't]=>[做不到。]

windmxf · 2017-06-19T15:10:15Z

TODO/gang-of-four-patterns-in-kotlin.md


-Although the **Singleton** is considered an anti-pattern these days, it has its usages (I won't discuss this topic here, just use it with caution).


[just use it with caution]=>[但需要谨慎地使用它。]

windmxf · 2017-06-19T15:13:45Z

TODO/gang-of-four-patterns-in-kotlin.md

@@ -197,13 +197,13 @@ execute {
 }
 ```

-As you can see, there is no need to have a class at all! One could argue, that this now resembles the **Strategy** pattern, which is probably correct. But then again, **Strategy** and **Template Method** are solving very similar problems (if not the same).


[As you can see, there is no need to have a class at all!]=>[可以看到，这里不需要写任何一个类！]

windmxf · 2017-06-19T15:19:59Z

TODO/gang-of-four-patterns-in-kotlin.md


-Writing an **Iterator** is a rare task. Most of the time, it's easier and more convenient to wrap a `List` and implement the `Iterable` interface.


[Writing an Iterator is a rare task]=>[很少需要自己写一个迭代器。]

windmxf · 2017-06-19T15:21:33Z

TODO/gang-of-four-patterns-in-kotlin.md


-In Kotlin, `iterator()` is an operator function. This means that when a class defines a function `operator fun iterator()`, it can be iterated using a `for` loop (no interface needed). That's particularly cool because it works also with extension functions. That's right - by using an extension function, I can make *every* object iterable. Consider this example:


[That's particularly cool]=>[这种方式非常酷。]

windmxf · 2017-06-19T15:27:41Z

TODO/gang-of-four-patterns-in-kotlin.md


-I hope this post gave you an idea on how Kotlin can result in different approaches to well known problems.


[-I hope this post gave you an idea on how Kotlin can result in different approaches to well known problems.]=>[希望这篇文章能给你些启发，让你了解用Kotlin可以带来新的思路来解决那些广为人知的问题。]

进行了一些修改，感谢指正。

wilsonandusa · 2017-06-19T18:39:44Z

校对认领 @sqrthree

linhe0x0 · 2017-06-20T02:16:01Z

@wilsonandusa 好哒

wilsonandusa · 2017-06-21T02:35:30Z

TODO/gang-of-four-patterns-in-kotlin.md


-The goal is not to simply *implement* the patterns, though. Since Kotlin supports object oriented programming and is interoperable with Java, I could just copy-auto-convert every java class in Mario's repository (doesn't matter whether it's the "traditional" or the "lambda" examples) and **it would still work!**
+当然，我的目标不是简单的 **实现** 这些模式。因为 Kotlin 支持面向对象编程并且和 Java 是可互操作的，我可以从 Mario 的仓库直接复制粘贴每一个 Java 文件（先不管是“传统”的还是“lambada 风格”的），**它们将仍然可以正常工作**！



typo: [lambada] => [lambda]

wilsonandusa · 2017-06-21T02:41:30Z

TODO/gang-of-four-patterns-in-kotlin.md


-That's why —just like Mario in the `g ∘ f` repository— I will try to find a simpler, easier or more idiomatic way to solve the same problem each pattern is solving.
+这就是为什么我像 Mario 那样，去寻找一种更简单方便、更惯用的方式来解决这些模式所要解决的问题。



g of f 地址(https://github.com/mariofusco/from-gof-to-lambda) 可以考虑加上

wilsonandusa

校对完成。翻译的不错

wilsonandusa · 2017-06-22T01:54:28Z

TODO/gang-of-four-patterns-in-kotlin.md

@@ -1,44 +1,44 @@
 > * 原文地址：[Gang of Four Patterns in Kotlin](https://dev.to/lovis/gang-of-four-patterns-in-kotlin)
 > * 原文作者：[Lovis](https://dev.to/lovis)
 > * 译文出自：[掘金翻译计划](https://github.com/xitu/gold-miner)
-> * 译者：
+> * 译者：[Boiler Yao](https://github.com/boileryao)
 > * 校对者：


校对者：wilsonandusa

wilsonandusa

添加了校对者

changed according to the advices, added passage info

boileryao · 2017-06-22T02:29:41Z

校对完成 @sqrthree

linhe0x0 · 2017-06-22T02:51:34Z

@boileryao @windmxf 的 review 还有许多没有折叠，是不需要调整吗？还是需要讨论下？麻烦 @windmxf 确认下哈。

linhe0x0

还有一个小问题需要调整下哈

linhe0x0 · 2017-06-22T02:52:36Z

TODO/gang-of-four-patterns-in-kotlin.md


 ---

-As you might know, there are three types of (gof) patterns: **structural**, **creational** and **behavioral** patterns.
+众所周知，根据“四人帮”的定义设计模式可以分为三种: **结构型**、**创建型 **和 **行为型**。


boileryao · 2017-06-22T04:57:01Z

好啦 @sqrthree
掘金地址：https://juejin.im/post/594b2ac00ce4630057425bd5

translated

6a625f3

linhe0x0 added Android 校对认领 labels Jun 19, 2017

linhe0x0 mentioned this pull request Jun 19, 2017

当设计模式遇上 Kotlin #1761

Closed

linhe0x0 added the 正在校对 label Jun 19, 2017

windmxf reviewed Jun 19, 2017

View reviewed changes

update

76f7d41

进行了一些修改，感谢指正。

linhe0x0 removed the 校对认领 label Jun 20, 2017

wilsonandusa reviewed Jun 21, 2017

View reviewed changes

wilsonandusa reviewed Jun 22, 2017

View reviewed changes

update

78f0145

changed according to the advices, added passage info

linhe0x0 requested changes Jun 22, 2017

View reviewed changes

modified a render failure

5fcaa5d

修改了一下 Markdown 标记的问题

2b80d66

linhe0x0 approved these changes Jun 22, 2017

View reviewed changes

linhe0x0 merged commit 63f139c into xitu:master Jun 22, 2017

linhe0x0 added 翻译完成 and removed 正在校对 labels Jun 22, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

当设计模式遇上 Kotlin #1780

当设计模式遇上 Kotlin #1780

boileryao commented Jun 19, 2017

windmxf commented Jun 19, 2017

linhe0x0 commented Jun 19, 2017

windmxf left a comment

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

windmxf Jun 19, 2017

wilsonandusa commented Jun 19, 2017 •

edited

Loading

linhe0x0 commented Jun 20, 2017

wilsonandusa Jun 21, 2017

wilsonandusa Jun 21, 2017

wilsonandusa left a comment

wilsonandusa Jun 22, 2017

wilsonandusa left a comment

boileryao commented Jun 22, 2017

linhe0x0 commented Jun 22, 2017

linhe0x0 left a comment

linhe0x0 Jun 22, 2017

boileryao commented Jun 22, 2017


		It's also important to note that these patterns where discovered to overcome the shortcomings of how imperative programming languages were designed in the 90s (C++ in particular). Many modern languages provide features to overcome these issues without writing extra code or falling back to patterns.
		认识到这些模式的发明是为了弥补起源于上世纪九十年代的一些命令式编程语言（尤其是 C++）的不足是很重要的。很多现代编程语言提供了解决这些不足的特性，我们完全不需要再写多余的代码或者做刻意模仿设计模式这种事了。


		Inspired by Mario Fusco's [Talk](https://www.youtube.com/watch?v=Rmer37g9AZM)/[Blog posts](https://www.voxxed.com/blog/2016/04/gang-four-patterns-functional-light-part-1/)/[Repository](https://github.com/mariofusco/from-gof-to-lambda) "From GoF to lambda", I decided to implement some of the most famous design patterns in computer science in Kotlin!


		That's why —just like Mario in the `g ∘ f` repository— I will try to find a simpler, easier or more idiomatic way to solve the same problem each pattern is solving.


		If you don't like reading explanations, you can directly jump to my [github repository](https://github.com/lmller/gof-in-kotlin)


		First up are the structural patterns. This is tough, because structural patterns are about - structure! How could I implement a structure with a different structure? I can't. An exception is the Decorator. While it's technically just about structure, its usage is more about behavior or responsibilities.


		Although the Singleton is considered an anti-pattern these days, it has its usages (I won't discuss this topic here, just use it with caution).


		Writing an Iterator is a rare task. Most of the time, it's easier and more convenient to wrap a `List` and implement the `Iterable` interface.


		In Kotlin, `iterator()` is an operator function. This means that when a class defines a function `operator fun iterator()`, it can be iterated using a `for` loop (no interface needed). That's particularly cool because it works also with extension functions. That's right - by using an extension function, I can make every object iterable. Consider this example:


		I hope this post gave you an idea on how Kotlin can result in different approaches to well known problems.


		The goal is not to simply implement the patterns, though. Since Kotlin supports object oriented programming and is interoperable with Java, I could just copy-auto-convert every java class in Mario's repository (doesn't matter whether it's the "traditional" or the "lambda" examples) and it would still work!
		当然，我的目标不是简单的实现这些模式。因为 Kotlin 支持面向对象编程并且和 Java 是可互操作的，我可以从 Mario 的仓库直接复制粘贴每一个 Java 文件（先不管是“传统”的还是“lambada 风格”的），它们将仍然可以正常工作！


		That's why —just like Mario in the `g ∘ f` repository— I will try to find a simpler, easier or more idiomatic way to solve the same problem each pattern is solving.
		这就是为什么我像 Mario 那样，去寻找一种更简单方便、更惯用的方式来解决这些模式所要解决的问题。

当设计模式遇上 Kotlin #1780

当设计模式遇上 Kotlin #1780

Conversation

boileryao commented Jun 19, 2017

windmxf commented Jun 19, 2017

linhe0x0 commented Jun 19, 2017

windmxf 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wilsonandusa commented Jun 19, 2017 • edited Loading

linhe0x0 commented Jun 20, 2017

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wilsonandusa left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

wilsonandusa left a comment

Choose a reason for hiding this comment

boileryao commented Jun 22, 2017

linhe0x0 commented Jun 22, 2017

linhe0x0 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

boileryao commented Jun 22, 2017

wilsonandusa commented Jun 19, 2017 •

edited

Loading