Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
int
Rust
提交
d46b8f1f
R
Rust
项目概览
int
/
Rust
大约 1 年 前同步成功
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
Rust
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
d46b8f1f
编写于
1月 05, 2015
作者:
A
Alex Crichton
浏览文件
操作
浏览文件
下载
差异文件
rollup merge of #19235: bjz/reference
cc. @steveklabnik
上级
c7dd3c4d
144f4b88
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
22 addition
and
67 deletion
+22
-67
src/doc/reference.md
src/doc/reference.md
+22
-67
未找到文件。
src/doc/reference.md
浏览文件 @
d46b8f1f
...
...
@@ -4316,73 +4316,28 @@ fine-grained control is desired over the output format of a Rust crate.
*TODO*
.
# Appendix: Influences and further references
## Influences
> The essential problem that must be solved in making a fault-tolerant
> software system is therefore that of fault-isolation. Different programmers
> will write different modules, some modules will be correct, others will have
> errors. We do not want the errors in one module to adversely affect the
> behaviour of a module which does not have any errors.
>
> — Joe Armstrong
> In our approach, all data is private to some process, and processes can
> only communicate through communications channels. *Security*, as used
> in this paper, is the property which guarantees that processes in a system
> cannot affect each other except by explicit communication.
>
> When security is absent, nothing which can be proven about a single module
> in isolation can be guaranteed to hold when that module is embedded in a
> system [...]
>
> — Robert Strom and Shaula Yemini
> Concurrent and applicative programming complement each other. The
> ability to send messages on channels provides I/O without side effects,
> while the avoidance of shared data helps keep concurrent processes from
> colliding.
>
> — Rob Pike
Rust is not a particularly original language. It may however appear unusual by
contemporary standards, as its design elements are drawn from a number of
"historical" languages that have, with a few exceptions, fallen out of favour.
Five prominent lineages contribute the most, though their influences have come
and gone during the course of Rust's development:
*
The NIL (1981) and Hermes (1990) family. These languages were developed by
Robert Strom, Shaula Yemini, David Bacon and others in their group at IBM
Watson Research Center (Yorktown Heights, NY, USA).
*
The Erlang (1987) language, developed by Joe Armstrong, Robert Virding, Claes
Wikstr
ö
m, Mike Williams and others in their group at the Ericsson Computer
Science Laboratory (
Ä
lvsj
ö
, Stockholm, Sweden) .
*
The Sather (1990) language, developed by Stephen Omohundro, Chu-Cheow Lim,
Heinz Schmidt and others in their group at The International Computer
Science Institute of the University of California, Berkeley (Berkeley, CA,
USA).
*
The Newsqueak (1988), Alef (1995), and Limbo (1996) family. These
languages were developed by Rob Pike, Phil Winterbottom, Sean Dorward and
others in their group at Bell Labs Computing Sciences Research Center
(Murray Hill, NJ, USA).
*
The Napier (1985) and Napier88 (1988) family. These languages were
developed by Malcolm Atkinson, Ron Morrison and others in their group at
the University of St. Andrews (St. Andrews, Fife, UK).
Additional specific influences can be seen from the following languages:
*
The structural algebraic types and compilation manager of SML.
*
The attribute and assembly systems of C#.
*
The references and deterministic destructor system of C++.
*
The memory region systems of the ML Kit and Cyclone.
*
The typeclass system of Haskell.
*
The lexical identifier rule of Python.
*
The block syntax of Ruby.
# Appendix: Influences
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: algebraic datatypes, pattern matching, type inference,
semicolon statement separation
*
C++: references, RAII, smart pointers, move semantics, monomorphisation,
memory model
*
ML Kit, Cyclone: region based memory management
*
Haskell (GHC): typeclasses, type families
*
Newsqueak, Alef, Limbo: channels, concurrency
*
Erlang: message passing, task failure, ~~linked task failure~~,
~~lightweight concurrency~~
*
Swift: optional bindings
*
Scheme: hygienic macros
*
C#: attributes
*
Ruby: ~~block syntax~~
*
NIL, Hermes: ~~typestate~~
*
[
Unicode Annex #31
](
http://www.unicode.org/reports/tr31/
)
: identifier and
pattern syntax
[
ffi
]:
guide-ffi.html
[
plugin
]:
guide-plugin.html
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录