rspotify VS rust

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.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.