- Mastering Rust
- Rahul Sharma Vesa Kaihlavirta
- 251字
- 2021-07-02 13:35:26
Writing documentation
To write documentation, we have special symbols for marking the start of documentation comments (doc comments hereafter). Docs are written in a similar fashion, the way we write comments, but they are treated differently compared to ordinary comments and are parsed by rustdoc. The doc comments are divided into two levels and use separate symbols to mark the start of the doc comment:
- Item level: These comments are meant for items within the module such as structs, enum declarations, functions, trait constants, and so on. They should appear above the item. For single-line comments, they start with ///, while multi-line comments begin with /** and end with */.
- Module level: These are comments that appear at the root level, i.e., main.rs, lib.rs, or any other module, and use //! to mark the start of a line comment – or /*! for multi-line comments – before ending them with */. They are suitable for giving a general overview of your crate and example usage.
Within the doc comment, you can write docs using the usual markdown syntax. It also supports writing valid Rust code within backticks (```let a = 23;```), which becomes part of documentation tests.
The preceding notation for writing comments is actually a syntatic sugar for the #[doc="your doc comment"] attribute. These are called doc attributes. When rustdoc parses the /// or /** lines, it converts them into these doc attributes. Alternatively, you can also write docs using these doc attributes.
- Reporting with Visual Studio and Crystal Reports
- 深入淺出Electron:原理、工程與實踐
- PyTorch自動駕駛視覺感知算法實戰
- C語言程序設計
- Quarkus實踐指南:構建新一代的Kubernetes原生Java微服務
- Visual C++數字圖像處理技術詳解
- PySide GUI Application Development(Second Edition)
- Spring+Spring MVC+MyBatis整合開發實戰
- OpenStack Orchestration
- Web前端應用開發技術
- CRYENGINE Game Development Blueprints
- C++ Application Development with Code:Blocks
- C++從入門到精通(第6版)
- Learning C++ by Creating Games with UE4
- Raspberry Pi Blueprints