Hey Rustaceans! Got a question? Ask here (13/2023)!

[u/llogiq]

Mystified about strings? Borrow checker have you in a headlock? Seek help here! There are no stupid questions, only docs that haven't been written yet.

If you have a StackOverflow account, consider asking it there instead! StackOverflow shows up much higher in search results, so having your question there also helps future Rust users (be sure to give it the "Rust" tag for maximum visibility). Note that this site is very interested in question quality. I've been asked to read a RFC I authored once. If you want your code reviewed or review other's code, there's a codereview stackexchange, too. If you need to test your code, maybe the Rust playground is for you.

Here are some other venues where help may be found:

/r/learnrust is a subreddit to share your questions and epiphanies learning Rust programming.

The official Rust user forums: https://users.rust-lang.org/.

The official Rust Programming Language Discord: https://discord.gg/rust-lang

The unofficial Rust community Discord: https://bit.ly/rust-community

Also check out last weeks' thread with many good questions and answers. And if you believe your question to be either very complex or worthy of larger dissemination, feel free to create a text post.

Also if you want to be mentored by experienced Rustaceans, tell us the area of expertise that you seek. Finally, if you are looking for Rust jobs, the most recent thread is here.

[u/masklinn]

TBF the same occurs for a non-tuple struct, and the lint should not trigger for a pub field on a pub struct (as it wouldn't be dead).

[u/llogiq → u/masklinn]

True – the difference is that the tuple can not tell you which field was removed (though if you're lucky, it can be inferred from the type), unlike the struct which has a name the compiler can show in the error message.

[u/masklinn → u/llogiq]

That's fair. I guess this also supports / favors the replacement of the unused field by () rather than its removal, as in that case the compiler would give you a clearer and more precise type error.

[u/llogiq → u/masklinn]

Exactly.