我可以避免使用显式生命周期说明符而是使用引用计数（Rc）吗？

Question

I am reading the Rust Book and everything was pretty simple to understand (thanks to the book's authors), until the section about lifetimes . I spent all day, reading a lot of articles on lifetimes and still I am very insecure about using them correctly.

What I do understand, though, is that the concept of explicit lifetime specifiers aims to solve the problem of dangling references. I also know that Rust has reference-counting smart pointers ( Rc ) which I believe is the same as shared_ptr in C++, which has the same purpose: to prevent dangling references.

Given that those lifetimes are so horrendous to me, and smart pointers are very familiar and comfortable for me (I used them in C++ a lot), can I avoid the lifetimes in favor of smart pointers? Or are lifetimes an inevitable thing that I'll have to understand and use in Rust code?

Answer 1

are lifetimes an inevitable thing that I'll have to understand and use in Rust code?

In order to read existing Rust code, you probably don't need to understand lifetimes. The borrow-checker understands them so if it compiles then they are correct and you can just review what the code does.

I am very insecure about using them correctly.

The most important thing to understand about lifetimes annotations is that they do nothing. Rather, they are a way to express to the compiler the relationship between references. For example, if an input and output to a function have the same lifetime, that means that the output contains a reference to the input (or part of it) and therefore is not allowed to live longer than the input. Using them "incorrectly" means that you are telling the compiler something about the lifetime of a reference which it can prove to be untrue - and it will give you an error, so there is nothing to be insecure about!

can I avoid the lifetimes in favor of smart pointers?

You could choose to avoid using references altogether and use Rc everywhere. You would be missing out on one of the big features of Rust: lifetimes and references form one of the most important zero-cost abstractions, which enable Rust to be fast and safe at the same time. There is code written in Rust that nobody would attempt to write in C/C++ because a human could never be absolutely certain that they haven't introduced a memory bug. Avoiding Rust references in favour of smart pointers will mostly result in slower code, because smart pointers have runtime overhead.

Many APIs use references. In order to use those APIs you will need to have at least some grasp of what is going on.

The best way to understand is just to write code and gain an intuition from what works and what doesn't. Rust's error messages are excellent and will help a lot with forming that intuition.