Analysis of information sources in references of the Wikipedia article "Rust" in Chinese language version.
[Brendan Eich]提出，每一年，瀏覽器都會在Pwn2Own競賽上發現新的漏洞。他說，Rust「不允許自由讀取記憶體」，但C++則可以。這些便是「導致瀏覽器弱點」，也是能夠自編譯的Rust要解決的問題。
Papers that have had more or less influence on Rust, or which one might want to consult for inspiration or to understand Rust's background. [...] Region based memory management in Cyclone [...] Safe memory management in Cyclone
The `if let` construct is based on the precedent set by Swift, which introduced its own `if let` statement.
Sources of Inspiration: [...] Rust
They are inspired by linear types, Uniqueness Types in the Clean programming language, and ownership types and borrowed pointers in the Rust programming language.
I just added the outline of a Result library that lets you use richer error messages. It's like Either except the names are more helpful. The names are inspired by Rust's Result library.
GH：在其他程式語言中有很多好的、討人喜愛的想法，沒有被廣泛採用的系統程式語言採納...在1970和80年代時，有些相當不錯的競爭者同時存在，我想要把它們所有的某些特性再拿出來，因為現況已經改變：網際網路是併發性非常強的系統，也更加重視安全性，所以以往獨鍾C以及C++的優勢不再成立。
...當然，為了更大程度的記憶體分享，使用者可以實作更複雜的資料結構，並同時保持介面只由被擁有和被管理的參照所組成。如此便解決了競爭存取和懸空指標的問題。
After that last change fixing the logging scope context bug, looks like stage1/rustc builds. Just shy of midnight :)
The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.
...想要維持和C一樣快又同時保證安全是不可能的...C++在設計上允許各種低層操作，大部分與迴避型態系統有關，藉此C++有了幾乎無限制的最佳化能力。不過在實際上，C++工程師在自己的程式碼中只使用某些特定的工具或技巧，例如透過pass by alias傳遞stack變數、獨特擁有的物件(通常是auto_ptr或C++0x的unique_ptr)、使用shared_ptr來達成「引用計數」、COM等等。Rust的型態系統的設計目標之一，就是在語言中融入這些安全性設計，並且強迫實行這些原則。這樣的話，效能可以與C++比較，又能同時保持記憶體安全...
Rust is not a particularly original language, with design elements coming from a wide range of sources. Some of these are listed below (including elements that have since been removed): SML, OCaml [...] C++ [...] ML Kit, Cyclone [...] Haskell [...] Newsqueak, Alef, Limbo [...] Erlang [...] Swift [...] Scheme [...] C# [...] Ruby [...] NIL, Hermes
At Mozilla Summit 2010, we launched Rust, a new programming language motivated by safety and concurrency for parallel hardware, the “manycore” future which is upon us.
Rust is not a particularly original language, with design elements coming from a wide range of sources. Some of these are listed below (including elements that have since been removed): SML, OCaml [...] C++ [...] ML Kit, Cyclone [...] Haskell [...] Newsqueak, Alef, Limbo [...] Erlang [...] Swift [...] Scheme [...] C# [...] Ruby [...] NIL, Hermes
Papers that have had more or less influence on Rust, or which one might want to consult for inspiration or to understand Rust's background. [...] Region based memory management in Cyclone [...] Safe memory management in Cyclone
The `if let` construct is based on the precedent set by Swift, which introduced its own `if let` statement.
Sources of Inspiration: [...] Rust
I just added the outline of a Result library that lets you use richer error messages. It's like Either except the names are more helpful. The names are inspired by Rust's Result library.
They are inspired by linear types, Uniqueness Types in the Clean programming language, and ownership types and borrowed pointers in the Rust programming language.
The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.
After that last change fixing the logging scope context bug, looks like stage1/rustc builds. Just shy of midnight :)
GH：在其他程式語言中有很多好的、討人喜愛的想法，沒有被廣泛採用的系統程式語言採納...在1970和80年代時，有些相當不錯的競爭者同時存在，我想要把它們所有的某些特性再拿出來，因為現況已經改變：網際網路是併發性非常強的系統，也更加重視安全性，所以以往獨鍾C以及C++的優勢不再成立。
...想要維持和C一樣快又同時保證安全是不可能的...C++在設計上允許各種低層操作，大部分與迴避型態系統有關，藉此C++有了幾乎無限制的最佳化能力。不過在實際上，C++工程師在自己的程式碼中只使用某些特定的工具或技巧，例如透過pass by alias傳遞stack變數、獨特擁有的物件(通常是auto_ptr或C++0x的unique_ptr)、使用shared_ptr來達成「引用計數」、COM等等。Rust的型態系統的設計目標之一，就是在語言中融入這些安全性設計，並且強迫實行這些原則。這樣的話，效能可以與C++比較，又能同時保持記憶體安全...
[Brendan Eich]提出，每一年，瀏覽器都會在Pwn2Own競賽上發現新的漏洞。他說，Rust「不允許自由讀取記憶體」，但C++則可以。這些便是「導致瀏覽器弱點」，也是能夠自編譯的Rust要解決的問題。
...當然，為了更大程度的記憶體分享，使用者可以實作更複雜的資料結構，並同時保持介面只由被擁有和被管理的參照所組成。如此便解決了競爭存取和懸空指標的問題。
At Mozilla Summit 2010, we launched Rust, a new programming language motivated by safety and concurrency for parallel hardware, the “manycore” future which is upon us.
