Write Rustier Rust

Показать описание

Parsing in Rust, from beginner to advanced user. Covering the mental models you can use to write Rustier Rust.

Рекомендации по теме

Комментарии

Unfortunately this was difficult to follow as code would be displayed for only brief periods.
I think it's fine to always show code and reduce screen switches - users are unlikely to get bored.

Regarding content, I'd like to see a perf or "panic-safety" comparison. Is there any difference between these solutions?

gajop

Here's how I'd do the problem:
fn paragraphs(input: &str) -> Vec<String> {
input
.split("\n\n")
.map(|p| p.replace("\n", " "))
.collect()
}

myronkipa

Great explanations!
I would recommend using fewer transitions from Code + Thumbnail to only you without the code. It makes it harder to follow, especially with the transition effects.

Drzhr

This video was awesome! You did a great job of walking from "acceptable" to "ideal", explaining why we might make those changes. I would love to see more videos like this, demonstrating some nice features from useful crates as you make the code better.

Galakyllz

At first I wrote clunky code. I learned more. I wrote clever code. I learned even more. Years later *I write clunky code on purpose*. Everyone on my team can trivially read it. Six months from now, I can trivially read it.

kurt

I could watch a ton of videos like this.
One idea: teach the standard library by refactoring imperative code into the stdlib alternatives.

pebaz

@5:41 I agree with your reasoning here. It may be nice to use expect() vs unwrap() so if the panic is reached due to the unwraps it can include your reasoning.

That_Guy_You_Know

Very informative video on just writing code that works and the ideal way to to write code(that also works). Got to learn a thing or two and also get to know about crates I never knew about before. Keep making more videos like this. We appreciate it

randomhunter

at 8:40 it's because concatenating Strings needs allocation, and the definition of coalesce enforces the same type for the closure args and for the closure's return types, hence we already need to feed it Strings instead of &str. I would however use !s.is_empty() consistently in this example, as checking len() for not zero is less readable ;)

MichaelKefeder

5:29 We don't need to make an anonymous function, we can just pass in the is_empty function: is_some_and(String::is_empty)

programming

This is less "Rustier" Rust and more of a nom tutorial.

Also, it seemed to me that the more Rusty the code got, the more unreadable and opaque it became.

Anyone can understand for loops and if statements. Fewer can understand fold / reduce. Even fewer will understand group_by and coalesce and all of the other itertools methods.

Even if you understand the functional concept, you'll still have to reach for documentation to make sure the programmed behaviour lines up with your expectation.

bryanleebmy

You basically introduced nom parser to me in your "advent of code" series. Thanks!

dj-maxus

Great video! A feedback to have video like that more enjoyable. The parts where you are explaining going fullscreen with webcam, it would be great to see a diff of the change (git style) it makes it much easier so understand at a glance.

Have a nice day and thanks again!

JagaSantagostino

Solid information!
I think it would be much easier to follow the information in the video if you didn't hide the code so quickly in certain parts. Having to go back and pause isn't ideal, and having to only listen to the audio at times feels pretty meaningless.

ohchristusername