Skip to content
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

Added section on compatibility and subsection on raw identifiers #1095

Merged
merged 1 commit into from
Aug 22, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions src/SUMMARY.md
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,10 @@
- [Integration testing](testing/integration_testing.md)
- [Dev-dependencies](testing/dev_dependencies.md)

- [Unsafe Operations](unsafe.md)

- [Compatibility](compatibility.md)
- [Raw identifiers](compatibility/raw_identifiers.md)

- [Meta](meta.md)
- [Documentation](meta/doc.md)

- [Unsafe Operations](unsafe.md)
7 changes: 7 additions & 0 deletions src/compatibility.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Compatibility

The Rust language is fastly evolving, and because of this certain compatibility
issues can arise, despite efforts to ensure forwards-compatibility wherever
possible.

* [Raw identifiers](compatibility/raw_identifiers.md)
42 changes: 42 additions & 0 deletions src/compatibility/raw_identifiers.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# Raw identifiers

Rust, like many programming languages, has the concept of "keywords".
These identifiers mean something to the language, and so you cannot use them in
places like variable names, function names, and other places.
Raw identifiers let you use keywords where they would not normally be allowed.
This is particularly useful when Rust introduces new keywords, and a library
using an older edition of Rust has a variable or function with the same name
as a keyword introduced in a newer edition.

For example, consider a crate `foo` compiled with the 2015 edition of Rust that
exports a function named `try`. This keyword is reserved for a new feature in
the 2018 edition, so without raw identifiers, we would have no way to name the
function.

```rust,ignore
extern crate foo;
fn main() {
foo::try();
}
```

You'll get this error:

```text
error: expected identifier, found keyword `try`
--> src/main.rs:4:4
|
4 | foo::try();
| ^^^ expected identifier, found keyword
```

You can write this with a raw identifier:

```rust,ignore
extern crate foo;
fn main() {
foo::r#try();
}
```
6 changes: 4 additions & 2 deletions src/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,12 @@ Now let's begin!

- [Testing](testing.html) - All sorts of testing in Rust.

- [Meta](meta.html) - Documentation, Benchmarking.

- [Unsafe Operations](unsafe.html)

- [Compatibility](compatibility.html)

- [Meta](meta.html) - Documentation, Benchmarking.


[rust]: https://www.rust-lang.org/
[install]: https://www.rust-lang.org/install.html
Expand Down