Alice Ryhl

But anyways, I think the Rust book is really good.

Other than that, I think, honestly, the way you learn a language is you have a project.

You implement some sort of project.

With it, I mean...

Maybe some sort of web server or something.

Yeah, it's totally a danger.

I recently tried using it for something where, I guess I was not writing Rust code, I was writing makefiles.

I wanted to add some support in the Linux kernel build system for some feature.

And it went into the makefile and added the Rust flags necessary to do it.

But then I looked at the code and it had added the necessary build flags.

But to the C side, it was passing a few more flags, which were not required per se, but they were there for a reason.

And it had just ignored them.

Any human looking at this would be like, why did you add Rust versions of all the flags?

I'm currently working on a new feature, which I think is really exciting.

It's something that we ran into in the Linux kernel, where we needed in-place initialization, the ability to construct values while knowing where they're being constructed so they don't get moved afterwards.

I'm pretty excited about our work to put that into the language, but it's very much ongoing.

I already mentioned the official Rust book.

I also think that, so John Gingset has another book that I think is really good.

And this book is kind of aimed at the intermediate Rust developer, the Rust developer who has gotten some Rust experience.

but wants to go further.