Repository navigation
print_debug example uses the <> structure syntax before it has been introduced #1871
Description
The print_debug example does, in fact, have a link at the bottom to the structure example page. But so far, the "<>" part of the structure syntax has not yet been introduced, and the print_debug page does not explain its meaning.
Interestingly, the linked page does not use or refer to this syntax, either.
The syntax may feel familiar to C++ and other developers who have encountered templates. But being new to this, I am not sure if this syntax exactly mimics the semantics in those other languages, and I am not sure we can assume all rust learners have even used another programming language with similar syntax.
The struct example page should almost certainly introduce the <> syntax and provide instances of its use.
Reacted by Glenn Vanderburg
Activity
marioidival commentedon Aug 10, 2024
I understand your point, but I think that RBE should be used as an auxiliary material for studies, that is, it is expected (in my opinion) that before studying using RBE, the learner has at least started the rust book.
Armer7 commentedon Nov 24, 2025
Then, in the learn section for the second column, where you refer to “Check out Rust by Example!”, write that the code is incomplete and not executable. For a complete understanding, read the main guide. I am a beginner. I need a short course (junior) to understand the syntax and basics of Rust. I saw this section and thought it would help me. But already on the second page, the code doesn't work when I try to implement it locally on my computer, and I have to spend three times as much time to understand what the problem is, since I don't know the language, I don't understand what's going on here and why there's an error. It turns out that I need to write just as much code to make this “piece of code” work. This is a bad approach for people who want to learn this language. You are pushing people away from it. Any code, if it guarantees execution, should work not only on your page, because there are a lot of caveats under the hood (you also need to warn about the caveats). If it is not complete, then write that this code is not complete and requires a thorough study of such sections of the language. I no longer want to study it according to your “instructions.”
marioidival commentedon Nov 25, 2025
Hello!
Thank you for this honest feedback. Your frustration is valid and important.
You've touched on a critical point: beginners shouldn't have to waste time debugging incomplete examples. This drives people away from the language, and that's exactly the opposite of what we want.
Here's where you can help us:
Rust by Example is open-source, and feedback like yours is essential. You're seeing something that many beginners probably also see, but don't report.
Could you help us in one of these ways?
Your beginner's perspective is far too valuable - you see problems that people who already know Rust can't see anymore.
You don't need to be a Rust expert to contribute. Actually, it's precisely because you're a beginner that your feedback is gold.
What do you think? Would you be up for turning this frustration into a contribution that will help hundreds of other beginners?