为系统程序提供的Rust教程 [我在控制台上做了一点修改---yshi]
这个一个为有c/c++程序员的Rust教程 A Rust tutorial for experienced C and C++ programmers.
Jump to contents. Jump to contributing.
这份教程受众是那些已经知道指针和引用如何工作，系统编程概念比如整型宽度和内存管理的程序员。 我们打算主要概括Rust和c++之间的不同以使你快速上手Rust而不是浪费时间在那些你已经知道的无价值的事情上面。 This tutorial is intended for programmers who already know how pointers and references work and are used to systems programming concepts such as integer widths and memory management. We intend to cover, primarily, the differences between Rust and C++ to get you writing Rust programs quickly without lots of fluff you probably already know.
对于c++程序员来说，Rust是一种非常直观的语言。大多数的语法都很类似。最大的不同(以我的经验)是 在Rust中一些好的系统编程的模糊概念被编译器严格执行。这在一开始是令人恼火的-编译器不允许你做 你想做的事(至少在safe代码块中)，有时候你做的事本身是safe的，但是你不能说服编译器。 Hopefully, Rust is a pretty intuitive language for C++ programmers. Most of the syntax is pretty similar. The big difference (in my experience) is that the sometimes vague concepts of good systems programming are strictly enforced by the compiler. This can be infuriating at first - there are things you want to do, but the compiler won't let you (at least in safe code), and sometimes these things are safe, but you can't convince the compiler of that. However, you'll 但是你很快对什么是被编译器允许的形成一种直觉。向编译器表达你的内存安全的想法需要一些新的 甚至有时复杂的注释。但是如果你对泛型编程中对象和表达式生命周期有很深的理解，学起来就不会太难受。 quickly develop a good intuition for what is allowed. Communicating your own notions of memory safety to the compiler requires some new and sometimes complicated type annotations. But if you have a strong idea of lifetimes for your objects and experience with generic programming, they shouldn't be too tough to learn.
本教程起源自一个系列博客(http://featherweightmusings.blogspot.co.nz/search/label/rust-for-c). This tutorial started as a series of blog posts. 一部分是为了帮助我学习Rust(没有比解释给别人更好的办法来检查学习成果了) Partly as an aid for me (@nrc) learning Rust (there is no better way to check that you have learnt something than to try and explain it to somebody else) and partly because I found the existing resources for learning Rust 同时因为现有的学习Rust的资源不能令人满意-他们都花费了大量的时间在那些我已经知道并使用过基础上， 高层次直觉上的概念描述对我来说可能比低层次的直觉介绍更好。从那以后，虽然Rust文档越来越好了， 我还是认为现存的c++程序员是Rust语言很自然的观众，但是他们没有被特殊的照顾好。 unsatisfactory - they spent too much time on the basics that I already knew and used higher level intuitions to describe concepts that could better be explained to me using lower level intuitions. Since then, the documentation for Rust has got much better, but I still think that existing C++ programmers are an audience who are a natural target for Rust, but are not particularly well catered for.
内容 介绍-hello world 控制流 基础类型和运算符 独占指针 可借用指针 引用计数指针和裸指针 数据类型 析构-1 析构-2 静态数组和动态数组 图和内存分配竞技场 闭包和一等公民函数
- Introduction - Hello world!
- Control flow
- Primitive types and operators
- Unique pointers
- Borrowed pointers
- Rc and raw pointers
- Data types
- Destructuring pt 1
- Destructuring pt 2
- Arrays and vecs
- Graphs and arena allocation
- Closures and first-class functions
其他资源
- The Rust book/guide - the best place for learning Rust in general and probably the best place to go for a second opinion on stuff here or for stuff not covered.
- Rust API documentation - detailed documentation for the Rust libraries.
- The Rust reference manual - a little out of date in places, but thorough; good for looking up details.
- Discuss forum - general forum for discussion or questions about using and learning Rust.
- StackOverflow Rust questions - answers to many beginner and advanced questions about Rust, but be careful though - Rust has changed a lot over the years and some of the answers might be very out of date.
Yes please!
If you spot a typo or mistake, please submit a PR, don't be shy! Please feel free to file an issue for larger changes or for new chapters you'd like to see. I'd also be happy to see re-organisation of existing work or expanded examples, if you feel the tutorial could be improved in those ways.
If you'd like to contribute a paragraph, section, or chapter please do! If you want ideas for things to cover, see the list of issues, in particular those tagged new material. If you're not sure of something, please get in touch by pinging me here (@nrc) or on irc (nrc, on #rust or #rust-internals).
Obviously, the intended audience is C++ programmers. The tutorial should concentrate on things that will be new to experienced C++ programmers, rather than a general audience (although, I don't assume the audience is familiar with the most recent versions of C++). I'd like to avoid too much basic material and definitely avoid too much overlap with other resources, in particular the Rust guide/book.
Work on edge case use cases (e.g., using a different build system from Cargo, or writing syntax extensions, using unstable APIs) is definitely welcome, as is in-depth work on topics already covered at a high level.
I'd like to avoid recipe-style examples for converting C++ code to Rust code, but small examples of this kind are OK.
Use of different formats (e.g., question and answer/FAQs, or larger worked examples) are welcome.
I don't plan on adding exercises or suggestions for mini-projects, but if you're interested in that, let me know.
I'm aiming for a fairly academic tone, but not too dry. All writing should be in English (British English, not American English; although I would be very happy to have localisations/translations into any language, including American English) and be valid GitHub markdown. For advice on writing style, grammar, punctuation, etc. see the Oxford Style Manual or The Economist Style Guide. Please limit width to 80 columns. I am a fan of the Oxford comma.
Don't feel like work has to be perfect to be submitted, I'm happy to edit and I'm sure other people will be in the future.