Notes that contain useful information about the state of the book or point out useful, but mostly out of scope, information are in blockquotes that start with the word "Note:" in bold. Whenever that term is used outside of that chapter, it is usually a link to the section that has this definition.Īn example term is an example of a term being defined.ĭifferences in the language by which edition the crate is compiled under are in a blockquote that start with the words "Edition Differences:" in bold.Įdition Differences: In the 2015 edition, this syntax is valid that is disallowed as of the 2018 edition. Statements that define a term contain that term in italics. Like all technical books, this book has certain conventions in how it displays information. That said, there is no wrong way to read this book. If a link looks interesting, click it, and read about that section. In that case, just browse the table of contents until you see something you want to know more about, and just start reading. The second is to generally improve your knowledge of a facet of the language. If you didn't already know that the lifetime of temporaries is defined in the expressions chapter, you could search "temporary let" and the first search result will take you to that section. Otherwise, you can press s or click the magnifying glass on the top bar to search for keywords related to your question.įor example, say you wanted to know when a temporary value created in a let statement is dropped. If you know which chapter answers that question, you can jump to that chapter in the table of contents. The first is to answer a specific question. There are two main ways to read this document. This book does not assume you are reading this book sequentially.Įach chapter generally can be read standalone, but will cross-link to other chapters for facets of the language they refer to, but do not discuss. We intend to produce such a book someday, and until then, the reference is the closest thing we have to one. It may include details that are specific to rustc itself, and should not be taken as a specification for the Rust language. You can only probe by running it, feeding it input and observing its output.Įverything that happens that way must conform to what the reference says. Instead, think of the compiled program as a black box. The reference does not specify what optimizations are allowed or disallowed. Rust compilers, including rustc, will perform optimizations. This book also only serves as a reference to what is available in stable Rust.įor unstable features being worked on, see the Unstable Book. There are a few pages such as linkage that still describe how rustc works. Similarly, this book does not usually document the specifics of rustc as a tool or of Cargo.Ĭargo has a book that contains a reference. Many of the features that one might expect to be language features are library features in Rust, so what you're looking for may be there, not here. Those libraries are documented separately by extracting documentation attributes from their source code. This book also does not serve as a reference to the standard library included in the language distribution. This book does not serve as an introduction to the language.īackground familiarity with the language is assumed.Ī separate book is available to help acquire such background familiarity. Prior versions can be found by adding the Rust version before the "reference" directory.įor example, the Reference for Rust 1.49.0 is located at. The latest release of this book, matching the latest Rust version, can always be found at. Tools ( rustc, cargo, etc.) and documentation ( Standard library, this book, etc.) are released with the language release. The first stable release of the language was Rust 1.0.0, followed by Rust 1.1.0 and so on. Rust has a new language release every six weeks. See the GitHub issues for what is not documented in this book. Macro Follow-Set Ambiguity Formal Specification Some content is licensed under the numpy license. Java is a registered trademark of Oracle and/or its affiliates. For details, see the Google Developers Site Policies. There are also some archived or unsupported language bindings:Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. We also provide the C++ API reference for TensorFlow Serving: We encourage the community to develop and maintain support for other languagesĪpproach recommended by the TensorFlow maintainers. Into projects and may offer some performance advantages in graph execution.Ī word of caution: the APIs in languages other than Python are not yet The Python API is at present the most completeĪnd the easiest to use, but other language APIs may be easier to integrate TensorFlow has APIs available in several languages both for constructing andĮxecuting a TensorFlow graph.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |