MARC details
000 -LEADER |
fixed length control field |
02048nam a22002537a 4500 |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
fixed length control field |
200605b2018 ||||| |||| 00| 0 eng d |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
International Standard Book Number |
9789352136834 |
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER |
Classification number |
005.133 BLA-J |
100 ## - MAIN ENTRY--PERSONAL NAME |
Personal name |
Blandy, Jim |
245 ## - TITLE STATEMENT |
Title |
Programming Rust : |
Remainder of title |
fast, safe systems development / |
Statement of responsibility, etc. |
Jim Blandy and Jason Orendorff |
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT) |
Place of publication, distribution, etc. |
India |
Name of publisher, distributor, etc. |
Shroff Publishers |
Date of publication, distribution, etc. |
2018 |
300 ## - PHYSICAL DESCRIPTION |
Extent |
598 p. |
365 ## - TRADE PRICE |
Price type code |
INR |
Price amount |
1575.00. |
500 ## - GENERAL NOTE |
General note |
Rust is a new systems programming language that combines the performance and low-level control of C and C++ with memory safety and thread safety. Rust’s modern, flexible types ensure your program is free of null pointer dereferences, double frees, dangling pointers, and similar bugs, all at compile time, without runtime overhead. In multi-threaded code, Rust catches data races at compile time, making concurrency much easier to use.<br/><br/>Written by two experienced systems programmers, this book explains how Rust manages to bridge the gap between performance and safety, and how you can take advantage of it. Topics include:<br/><br/>How Rust represents values in memory (with diagrams)<br/>Complete explanations of ownership, moves, borrows, and lifetimes<br/>Cargo, rustdoc, unit tests, and how to publish your code on crates.io, Rust’s public package repository<br/>High-level features like generic code, closures, collections, and iterators that make Rust productive and flexible<br/>Concurrency in Rust: threads, mutexes, channels, and atomics, all much safer to use than in C or C++<br/>Unsafe code, and how to preserve the integrity of ordinary code that uses it<br/>Extended examples illustrating how pieces of the language fit together. |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Programming languages (Electronic computers) |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Computer programming |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Rust (Computer program language) |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Software engineering |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Text editors (Computer programs) |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
UNIX (Computer file) |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
C (Computer program language) |
650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
Topical term or geographic name as entry element |
Domain-specific programming languages |
700 ## - ADDED ENTRY--PERSONAL NAME |
Personal name |
Orendorff, Jason |
952 ## - LOCATION AND ITEM INFORMATION (KOHA) |
Withdrawn status |
|