Andre Bogus - Easy Mode Rust 

God bless you

Glad you liked it.

I've done both, and I don't see a big difference here: With codegen you can start simple and output your generated code to ensure it is what you expect, in macros you can cargo expand to do mostly the same thing. Once things get complex, both ways offer little in the way of debugging.

Yeah, that was a deliberate joke. I am a dad of three, so I need to do at least one of those in each of my talks... 🙃

Well, it's not exactly cheating, and the only thing you incur by not following the suggestions is the need to learn the respective concepts. But for most of those things, building a lint would certainly be possible.

Isn't that what clippy is for? A lot of these things have lints you can enable for your codebase. Sometimes it even refactors the code for you.

@@yondaime500 well, yes and no. We do have a number of lints that will improve the "easy" Rust code people might write, but I don't know any that could be used to confine people to write easy style Rust code as of yet. We might add them in the future, but I don't see a lot of benefit to that.

@@llogiq Yeah, the former is what I meant, actually. For the latter, the only example I can think of is implicit_return. Maybe there are a few others in the restriction group.

​@@yondaime500 There are a great many lints that improve style, help find the right method combinations (len_zero, iter_skip_next) or even catch beginner mistakes (clone_on_copy) leading to incorrect code (let_underscore_lock, ineffective_bit_mask).

I think he means the easy mode to lecture someone or to start a project with begginers. From my understanding he is not trying to teach rust to the audiance... the rust book is a very nice place to begin the jouyrney, ot is free on rust site. Cheers

I agree. All the tips are just aweful xd

If the tips look awful to you, that's because you're looking at them from the wrong perspective. The idea behind my talk was to minimize the things people think they need to learn before they become productive in Rust. If you want to sell Rust to a startup, for example, the initial training costs are often cited as breaking the camel's back. So rest assured that despite my last name, I absolutely mean it.

You may have missed the premise of this talk -- the entire point is to explore the simplifications you can make to your code (in terms of how much Rust you must understand before writing that code) and their trade offs. I think these are good tips -- Rust is a complex language and I, as a beginner, wasted a lot of time trying to figure out how to write things more idiomatically when I should have just been getting the thing working (and let myself learn the idiomatic way to do things over time). A lot of the tips are almost reminders that there was a way people did these things before these language features existed and you can still do those things in Rust, which seems obvious but for some reason in the beginner's mind its often not.

This talk is none of those things. Your comment misses the point. To say Rust must always be rigid enforcement against potential errors, ruthless efficiency, and new users must be forced to accept ALL these things before they have even mastered the most basic of syntax issues... that position overlooks the many improvements outside of the borrow checker. To argue this is a "joke" is a hostile and narrow perspective, which you might expect on decades-old C Programming forums which slowly lose users. One should always have patience for those who learned differently than they did. Trying is trying. If another, easier language had a "Rust mode" that exactly matched Rust, would that be any different?