-
Notifications
You must be signed in to change notification settings - Fork 13.3k
document ref #3337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for all these documentation bugs -- it's very useful to know what's not covered! |
Agreed with @catamorphism. Thanks! |
It's certainly a problem to see what's not there. I added those based on a review of the commits since I had last pulled. Best thing would probably be to adopt a convention that all tests reference a section of the manual (or have a FIXME). |
It would be great to have some relationship between the manual and tests. A policy that all tests have links to documentation though would probably discourage writing tests. I wonder if there's a lighter process we could use. Note that all of the examples in the documentation are also tests. |
Upgrade toolchain to 7/12 Relevant PRs: rust-lang#127176 and rust-lang#125507 Resolves rust-lang#3319 By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.
Apparently ref can be used when binding variables during pattern matching, but I don't think that is documented. What is documented in 11.2 of the tutorial is "When you destructure on a value in a match expression, or loop over a vector with for, variables bound to the inside of the given data structure will use safe references, not copies" which I'm guessing is incorrect.
The text was updated successfully, but these errors were encountered: