Reviews
The translation is good, and the book is already a high-point book in Amazon, so it's pretty obvious that the material has been verified.
There's a lot of effort on the part of the conductor to make the text without errors, but it doesn't really make sense to any sentence that you read over and over again. If you have a very awkward part of a Korean sentence, please read the English original together.
I think it's something that you should see after seeing The content. And the basic part of é is that it makes sense.
The last time we talked about programming, we had a little taste of Python and C and we went to the Rust. I want to know more about it on the line than on the practical use. Because of the poor background of programming, the official guide had a little bit of a feel, and I'm glad this book has been elaborated. Similar to books about other rush, or other languages, you should know a little bit and be easy to read.
Unlike Theb, it's fun to have a very practical example from the beginning.
Jim Blandy et al.: Programming Rust
The book shows how the function of the rush, which adds predictable performance to memory safety and reliable synchronization, gives the programmer control of memory consumption and processor use. If you have experience, you can learn to successfully fill the gap between luthrum performance and safety with this practical guide.
Korean title: 프로그래밍 러스트
Korean author: 짐 블랜디 외
Korean publisher: 제이펍
ISBN-13: 9791192469751
Reviews
The translation is good, and the book is already a high-point book in Amazon, so it's pretty obvious that the material has been verified.
There's a lot of effort on the part of the conductor to make the text without errors, but it doesn't really make sense to any sentence that you read over and over again. If you have a very awkward part of a Korean sentence, please read the English original together.
I think it's something that you should see after seeing The content. And the basic part of é is that it makes sense.
The last time we talked about programming, we had a little taste of Python and C and we went to the Rust. I want to know more about it on the line than on the practical use. Because of the poor background of programming, the official guide had a little bit of a feel, and I'm glad this book has been elaborated. Similar to books about other rush, or other languages, you should know a little bit and be easy to read.
Unlike Theb, it's fun to have a very practical example from the beginning.
