I am noticing that there (seems, I'm a newbie here, sorry) to be several errors in the tutorials. Also, I have questions about some of the text surrounding the examples.
What is the best way to communicate these issues back to the community so that those with expertise in the tutorials can address them? Creating a separate topic for each one might not be very efficient, although there could be good reasons for doing things that way, too. Again, I'm new here and just learning the ropes.
As you reply, please keep in mind that these are problems with the tutorials themselves, not the rust language, per se. The sorts of things that create stumblebums for us newbies. IOW, I am not reporting problems with rust, or difficulties understanding rust itself. (Rust is probably just fine!)
[EDIT: I wonder if there is a way for the tutorial system to automatically report errors in unmodified examples so that they can be given immediate attention before a new user encounters them (allowing, of course, for those examples that are supposed to fail forcing the learner to correct the code). Since rust generates an error if the code doesn't compile, this should be fairly straightforward, and could be performed each time there is an update to rust, I think.]
I believe you. But can you be explicit about which tutorials?
The official books/tutorials tend to have GitHub repos where you can report issues and whatnot. PRs are probably even better if well written. Even then, it's a volunteer community effort to maintain everything, so I can't say how fast things would move.[1]
Going in circles I think. Each tutorial may be in a different repo. So you have to first tell us which tutorials, then someone can tell you where the repo it.
Everything else on that page can be found by clicking the GitHub logo except for the rust and web assembly book for whatever reason, but that does have a link on the first page:
So... it looks to me that the repo for all tutorials appears to be the same one in the rust github. Thus, all issues and problems can be reported to the "issues" list for the tutorials repo; there is no need to identify individual repo for a particular tutorial then?
Then it sounds like the thing you are calling “all tutorials” or “the tutorials” is the thing whose title is “Rust by Example“. We didn’t know what you meant because Rust by Example is not particularly thought of as “the tutorials”.
You should report an issue to the Rust by Example repo if the text is on one of the pages of Rust by Example, and not if it isn't. Including the URL for the particular page you are discussing is always appropriate, and while you copy and paste the URL you can check if it starts with https://doc.rust-lang.org/rust-by-example/ like all the Rust by Example pages do. If it doesn't, then you must be looking at a document that is not part of Rust by Example.
In general for arbitrary documentation sites, it isn't always clear what the relationship is or even what the repository is, but once you have a guess, checking if the title of the document and the URL of the document match the name of the repository you're creating an issue in should help.
My RBE notes are here -- part Cliff's Notes, half Issue material. I haven't reviewed it since I wrote it so it's possible there's been some drift. Feel free to browse.[1]
Going in circles I think. Each tutorial may be in a different repo. So you have to first tell us which tutorials, then someone can tell you where the repo it.