rspotify VS book

Apologies for the stupid question but I'm fairly new to Rust and can't figure out for the life of me how to use the rspotify crate. As far as I can get with the documentation / examples is just that it isn't a regular application / binary of itself but just a crate, but I don't see why that's causing me issues. Whenever I try to run the following example, I get the following error, despite me trying to remove and rebuild the crate just in case.

Link to the example code (Line 42)

I have wanted async generics myself for some time now. In RSpotify, we have both async and blocking users, so we had to resort to maybe_async to switch between them. However, this macro has a few caveats and isn't as convenient as having it built-in.

maybe_async accomplishes this by switching based on the feature flags enabled for your library. I found it in rspotify, but haven't actually given it a try myself.

As a developer of rspotify I'm curious as to why you chose not to use an already existing API client for Spotify. Are there any problems you found? I do agree that the current version is a mess but we're working on a full rewrite for 0.10 and you might be interested in that.

My first port of call was to google learn rust which lead me to "the book". The book is a first steps guide written by the rust community for newbies (or Rustlings as they're called) to gain a 'solid grasp of the language'.

Before Prodzilla, I’d read 'The Book' a couple of times, and had made my way through Rustlings, but hadn’t yet built a serious project in Rust.

To answer your last question;

Start with the Rust book.

https://doc.rust-lang.org/book/

Then do Rustlings until the syntax becomes muscle memory.

Then join the Discord and start doing little projects.

You won’t get up to the proficiency of other languages as quickly in Rust. It takes longer. For me it’s taking a lot longer, but I enjoy it.

Before diving into these repositories, familiarize yourself with Rust and its development ecosystem. The official Rust book is an excellent resource for developers at all levels. Each repository has documentation on how to contribute, covering code style, issue tracking, and pull requests.

This is my third Rust book after the official book and Rust in Action. The other two books are great, but they were too theoretical for me. I'm a slow learner and had much trouble grokking Rust's features and idiosyncrasies. When I was done with these books, I was lost and unsure of what I could do.

It's the same reason everything digital and downloadable isn't free: there's a cost to create it and there's a value to it.

For a language developer to charge for a book about that language, I think that's a completely valid way to make some money off of their work.

Even the Rust book, "The Rust Programming Language" is available freely online [0], but also as a print and ebook for sale via NoStarchPress [1].

[0] https://doc.rust-lang.org/book/

[1] https://nostarch.com/rust-programming-language-2nd-edition

You know you can just read it online right now in 2 different variants It does contain some systems programming.

I am looking at The Book (https://doc.rust-lang.org/book/), but hoped there was an amazing person on youtube.

Yeah, I'll build something, finally trying webassembly.

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