Gergely Orosz

It's now cleared, right?

This concept is new to me as someone who's not used Rust for sure.

It's very interesting.

One thing I've read is on forums, people complaining about so-called fighting the borrow checker.

What can make it challenging?

Yeah, I'm starting to understand why you mentioned that data structures were a place of learning coming from other languages.

Oftentimes the solution seems to be just think about your data structures, understand them, and do it in the Rust way, right?

We talked about memory safety, but there is a keyword in Rust called unsafe.

What does this do, and in what cases do people typically use?

When does it make sense to use, and why does it even exist?

That's just a naive question from me.

You want to avoid this check or if you're in a loop every time.

So unsafe will just avoid checks.

May that be as if runtime or compile time checks or both?

Got it.

And then in practice for sensible use cases of unsafe, is it usually to do with high performance code typically?

Or what cases have you seen which are like legitimate?

This is a great use case for unsafe.

Can we talk about the Rust ecosystem, the broader ecosystem?

And when it comes to this, the first thing that people come across, including myself, is the Crate ecosystem, Rust's package manager.