rust-typed-builder VS rustlings-solutions-5

derive_builder works in runtime - you have to unwrap built result. And code editors cannot use auto-import builder-types. That's why I switched to [typed-builder|https://github.com/idanarye/rust-typed-builder] which looks similar to builder-pattern but more popular.

I'm the author of the typed-builder crate (and a couple of other crates in a similar position). The name of the crate's repository on GitHub is rust-typed-builder. Does the new trademark policy mean I have to change the repository's name to typed-builder-rs or typed-builder.rs or something similar, or am I in the clear because only the repository name is has the word "rust" in it and the crate itself is only named "typed-builder"?

There are also crates which can do that for you (e.g. https://github.com/idanarye/rust-typed-builder).

I can open a PR if desired but typed-builder is a big example for me of where this would be super useful. It's a good example of using traits/type safety for compile-time guarantees but the error messages are really subpar compared to the standard Rust experience, so feels like a very arbitrary compromise on Rust's strengths.

Yes! The inspiration came from: * rust-typed-builder which is the struct equivalent of this crate. * https://users.rust-lang.org/t/typesafe-builder-design/58784

Rust Typed Builder

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/

i think you've found what i'm looking for! https://github.com/rust-lang/rustlings

I would recommend rustlings as a way to get used to semantics. It starts from absolute basics but it gave me a more intuitive understanding of the language.

go along with Rustlings https://github.com/rust-lang/rustlings

rustlings — Small exercises to get you used to reading & writing Rust code!

I had finished this Udemy course, which was a bit too fast towards the end but still enjoyable, I read THE BOOK and done the Rustlings (here are my old solutions and here the new ones).

You will get used to it when you write more Rust code. Read the book, implement some exercises and watch some tutorial YT videos, everything will make sense eventually.

Check out rustlings. Simple exercises with writing rust code, introducing new concepts along the way.

There's an official "book" that you can look up online. It goes through Rust step by step, like a tutorial. Alternatively there's the rustling's course where you learn Rust by doing small exercises. I have only ever looked at the book, which is fantastic. But if you know a bit of C and some sort of class-system like in OOP or Haskell's typeclasses you can just look up the syntax when you need to, it is really easy. Also, the compiler warnings/errors usually tell you what you need to do in order to fix your error (especially for simple stuff in the beginning) so often you don't even need to google the issue.

Rustlings might be useful to you: https://github.com/rust-lang/rustlings