- Rust Essentials(Second Edition)
- Ivo Balbaert
- 214字
- 2021-07-02 15:30:38
Comments
Ideally, a program should be self-documenting by using descriptive variable names and easy-to-read code, but there are always cases where additional comments about a program's structure or algorithms are needed. Rust follows the C convention and has:
- // line comments; everything on the line after // is commentary and not compiled
- /* */block or multi-line comments; everything between the start /*and the end */ is not compiled
However, the preferred Rust style is to use only the // comment, also for multiple lines, as shown in the following code:
// see Chapter 2/code/comments.rs fn main() { // Here starts the execution of the Game. // We begin with printing a welcome message: println!("Welcome to the Game!"); }
Use the /* */ comments only to comment out code.
Rust also has a doc comment with ///, useful in larger projects that require an official documentation for customers and developers. Such comments have to appear before an item (like a function) on a separate line to document that item. In these comments, you can use Markdown formatting syntax (see https://en.wikipedia.org/wiki/Markdown).
Here is a doc comment:
/// Start of the Game fn main() { }
We'll see more relevant uses of /// in later code snippets. The rustdoc tool can compile these comments into project documentation.
- LabVIEW 2018 虛擬儀器程序設計
- CentOS 7 Server Deployment Cookbook
- 深入淺出Java虛擬機:JVM原理與實戰
- Koa開發:入門、進階與實戰
- Java:Data Science Made Easy
- Functional Kotlin
- Mastering Predictive Analytics with Python
- Rust Essentials(Second Edition)
- The Complete Coding Interview Guide in Java
- 從零開始學C語言
- Getting Started with Nano Server
- Elasticsearch Essentials
- 平面設計經典案例教程:CorelDRAW X6
- Learning Kotlin by building Android Applications
- Serverless工程實踐:從入門到進階