Update description to reflect language changes #14809
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, the type system's restrictions on borrowing were summarized as > The previous example showed that the type system forbids any borrowing of owned boxes found in aliasable, mutable memory This did not jive with the example, which allowed mutations so long as the borrowed reference had been returned. Also, the language has changed to no longer allow aliasable mutable locations. This changes the summary to read > The previous example showed that the type system forbids mutations of owned boxed values while they are being borrowed. In general, the type system also forbids borrowing a value as mutable if it is already being borrowed - either as a mutable reference or an immutable one. This adds more general information for the experienced reader as well, to offer a more complete understanding.
bors
added a commit
that referenced
this pull request
Jun 12, 2014
Previously, the type system's restrictions on borrowing were summarized as > The previous example showed that the type system forbids any borrowing of owned boxes found in aliasable, mutable memory. This did not jive with the example, which allowed mutations so long as the borrowed reference had been returned. Also, the language has changed to no longer allow aliasable mutable locations. This changes the summary to read > The previous example showed that the type system forbids mutations of owned boxed values while they are being borrowed. In general, the type system also forbids borrowing a value as mutable if it is already being borrowed - either as a mutable reference or an immutable one. This adds more general information for the experienced reader as well, to offer a more complete understanding.
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Jun 5, 2023
Support `#[macro_use(name, ...)]` This PR adds support for another form of the `macro_use` attribute: `#[macro_use(name, ...)]` ([reference]). Note that this form of the attribute is only applicable to extern crate decls, not to mod decls. [reference]: https://doc.rust-lang.org/reference/macros-by-example.html#the-macro_use-attribute
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the type system's restrictions on borrowing were summarized as
This did not jive with the example, which allowed mutations so long as the borrowed reference had been returned. Also, the language has changed to no longer allow aliasable mutable locations. This changes the summary to read
This adds more general information for the experienced reader as well, to offer a more complete understanding.