I am a programmer who has about 10 years of experience with C++. Two years ago, I got to know about Rust when trying to find some alternatives for C++ in some big projects, as we often encountered some bugs that took quite a few days to trace the causes, especially then the systems were running in production mode and debugging was not possible. When I first had a look at Rust, I thought it would be a very good choice to solve our problems. However, not until recently do I have time to start learning some Rust programming. At first, I think learning Rust, especially from a C++ background will be quite easy (in fact, many C++ programmers will have the same thought), however it is a bit more difficult than I expected, and I need to invest a significant amount of time in order to get to a quite basic level in Rust programming. Of course, I know learning a total new system programming language is not easy, but in fact learning Rust to me is as difficult to learning C++ from scratch some 15 years ago.
Rust has been becoming more and more popular recently, but a paradox is that not many C++ programmers pay attention to Rust, as far as I know. Many of my friends, who are experienced in C++, either deny to learn Rust, or give it up after a short time, or do not have intention to use Rust for their work. Some even never hear about Rust.
My experience of learning Rust reveals that a C++ programmer can learn (basic) Rust much more quickly than normal if he can extract the similarities between the two languages. Although Rust is quite a radical programming language, we cannot deny that it shares many common ideas with modern C++. Therefore, I create a very short book that compares Rust to modern C++ with very basic examples, one by one in pair. These are very simple examples and are often used to guide programmers when they start to learn any new programming language.
The purpose of the book is by no mean to cover all aspects of Rust, it just gives a very quick introduction to C++ programmers so they can move to write programs in Rust as quick as possible. I expect a C++ programmer will need only about 30 minutes to read through the book and after that he can immediately write some of his first programs in Rust, just for fun first, then after some time of evaluation the features of Rust, he can determine whether to consider Rust to use in serious work. This will be helpful, since at the moment, many C++ programmers even do not want to give a try to Rust, or give up too early because getting into Rust takes more time than they expected.
Here is the link of the book : https://vnduongthanhtung.gitbooks.io/migrate-from-c-to-rust/content/
Since my knowledge about Rust is quite elementary, there can be issues with terminology and content in the book, so any review or suggestion would be appreciated.