サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ドラクエ3
rust-lang.github.io
Rust API Guidelines Checklist Naming (crate aligns with Rust naming conventions) Casing conforms to RFC 430 (C-CASE) Ad-hoc conversions follow as_, to_, into_ conventions (C-CONV) Getter names follow Rust convention (C-GETTER) Methods on collections that produce iterators follow iter, iter_mut, into_iter (C-ITER) Iterator type names match the methods that produce them (C-ITER-TY) Feature names are
This is a set of recommendations on how to design and present APIs for the Rust programming language. They are authored largely by the Rust library team, based on experiences building the Rust standard library and other crates in the Rust ecosystem. These are only guidelines, some more firm than others. In some cases they are vague and still in development. Rust crate authors should consider them
Introduction mdBook is a command line tool to create books with Markdown. It is ideal for creating product or API documentation, tutorials, course materials or anything that requires a clean, easily navigable and customizable presentation. Lightweight Markdown syntax helps you focus more on your content Integrated search support Color syntax highlighting for code blocks for many different language
Getting Started Welcome to Asynchronous Programming in Rust! If you're looking to start writing asynchronous Rust code, you've come to the right place. Whether you're building a web server, a database, or an operating system, this book will show you how to use Rust's asynchronous programming tools to get the most out of your hardware. What This Book Covers This book aims to be a comprehensive, up-
12. TODO: Asynchronous Design Patterns: Solutions and Suggestions NOTE: this guide is currently undergoing a rewrite after a long time without much work. It is work in progress, much is missing, and what exists is a bit rough. Introduction This book is a guide to asynchronous programming in Rust. It is designed to help you take your first steps and to discover more about advanced topics. We don't
Rust RFCs - RFC Book - Active RFC List The “RFC” (request for comments) process is intended to provide a consistent and controlled path for changes to Rust (such as new features) so that all stakeholders can be confident about the direction of the project. Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow. S
The book has moved Please go here.
このページを最初にブックマークしてみませんか?
『rust-lang.github.io』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く