README.md

Step 1: Concepts

These steps describe common and necessary-to-know concepts for everyday programming in Rust.

❗️Before completing this step you should complete all its sub-steps.

After doing them you should be able to answer the following questions:

• How do I recognize that data is allocated at the heap rather than at the stack? When data should be allocated at the heap?
• What is copying and cloning data in Rust? What's the difference? When and why should I use them?
• How can a single piece of data be owned by multiple parts of program? When and why is this commonly required?
• How borrowing rules may be violated? In what price? When and why is this commonly required?
• How to deal with owned and borrowed data simultaneously? When and why is this commonly required?
• How to share values between threads? What is Send and Sync markers? Why are they required, when should be used?
• How do static and dynamic dispatches differ? Why do they exist? When and why should I choose between them?
• Why ?Sized types exist? How are they used? Why should I care about them?
• Why phantom types exist? What problems do they solve?

The following articles may help you to sum up your experience:

• Wrapper Types in Rust: Choosing Your Guarantees
• Rust, Builder Pattern, Trait Objects, Box<T> and Rc<T>
• Rust's Built-in Traits, the When, How & Why
• Learn Rust With Entirely Too Many Linked Lists
• Rustonomicon: Subtyping and Variance
• Crust of Rust: Subtyping and Variance

Task

Estimated time: 2 days

Provide your own implementation of doubly linked list data structure. It should be thread safe without a necessity to use explicit synchronization primitives (like Arc<Mutex<T>>) on top of it.

❗️ Don't use unsafe for this task.

Prove your implementation correctness with tests. Provide both single-threaded and multi-threaded examples of usage.