-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Borrowchecker README.md #40793
Labels
A-borrow-checker
Area: The borrow checker
A-docs
Area: documentation for any part of the project, including the compiler, standard library, and tools
Comments
Seems like a mistake, yes.
The book is the only other thing, officially. |
steveklabnik
added
the
A-docs
Area: documentation for any part of the project, including the compiler, standard library, and tools
label
Mar 24, 2017
All right, I created a pull request for the README.md
I'll be going through the code then. Thanks for the info. |
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Apr 7, 2017
Correcting mistakes in the README.md Correcting the two mistakes in the README.md (issue rust-lang#40793)
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Apr 7, 2017
Correcting mistakes in the README.md Correcting the two mistakes in the README.md (issue rust-lang#40793)
PR was merged, this can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-borrow-checker
Area: The borrow checker
A-docs
Area: documentation for any part of the project, including the compiler, standard library, and tools
Hi,
While going through the documentation of the borrowchecker, I found that the section Checking mutability of immutable pointer types is repeated twice, which is probably a mistake (the second one should be aliasability). Same thing for mutable pointer types.
Is it a mistake or is it intended ?
I was also wondering if there is some newer documentation about Rust's borrow checker and where it is available (this one dates from 2015).
Thanks in advance.
The text was updated successfully, but these errors were encountered: