GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing doc.rust-lang.org — std - Rust Expand description§The Rust Standard LibraryThe Rust Standard Library is the foundation of portable Rust software, a
set of minimal and battle-tested shared abstractions for the broader Rust
ecosystem. It offers core types, like
§How to read this documentationIf you already know the name of what you are looking for, the fastest way to find it is to use the search button at the top of the page. Otherwise, you may want to jump to one of these useful sections: If this is your first time, the documentation for the standard library is written to be casually perused. Clicking on interesting things should generally lead you to interesting places. Still, there are important bits you don’t want to miss, so read on for a tour of the standard library and its documentation! Once you are familiar with the contents of the standard library you may begin to find the verbosity of the prose distracting. At this stage in your development you may want to press the “ Summary” button near the top of the page to collapse it into a more skimmable view. While you are looking at the top of the page, also notice the “Source” link. Rust’s API documentation comes with the source code and you are encouraged to read it. The standard library source is generally high quality and a peek behind the curtains is often enlightening. §What is in the standard library documentation?First of all, The Rust Standard Library is divided into a number of focused
modules, all listed further down this page. These modules are
the bedrock upon which all of Rust is forged, and they have mighty names
like Second, implicit methods on primitive types are documented here. This can be a source of confusion for two reasons:
So for example there is a page for the primitive type
Note the documentation for the primitives Third, the standard library defines The Rust Prelude, a small collection of items - mostly traits - that are imported into every module of every crate. The traits in the prelude are pervasive, making the prelude documentation a good entry point to learning about the library. And finally, the standard library exports a number of standard macros, and lists them on this page (technically, not all of the standard macros are defined by the standard library - some are defined by the compiler - but they are documented here the same). Like the prelude, the standard macros are imported by default into all crates. §Contributing changes to the documentationCheck out the Rust contribution guidelines here. The source for this documentation can be found on GitHub in the ‘library/std/’ directory. To contribute changes, make sure you read the guidelines first, then submit pull-requests for your suggested changes. Contributions are appreciated! If you see a part of the docs that can be improved, submit a PR, or chat with us first on Zulip #t-libs. §A Tour of The Rust Standard LibraryThe rest of this crate documentation is dedicated to pointing out notable features of The Rust Standard Library. §Containers and collectionsThe The standard library exposes three common ways to deal with contiguous regions of memory:
Slices can only be handled through some kind of pointer, and as such come in many flavors such as:
For converting to strings use the Data may be shared by placing it in a reference-counted box or the The §Platform abstractions and I/OBesides basic data types, the standard library is largely concerned with abstracting over differences in common platforms, most notably Windows and Unix derivatives. Common types of I/O, including files, TCP, and UDP, are defined in
the The §Use before and after
|
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |