Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Commit

Permalink
overhaul
Browse files Browse the repository at this point in the history
  • Loading branch information
nikomatsakis committed Sep 3, 2021
1 parent 63256b8 commit 3a9308b
Show file tree
Hide file tree
Showing 5 changed files with 10 additions and 12 deletions.
4 changes: 2 additions & 2 deletions src/SUMMARY.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Summary

- [What is this?](./what_is_this.md)
- [What makes Rust empowering?](./how_rust_feels.md)
- [Rust's goals](./goals.md)
- [How Rust ought to feel](./how_rust_feels.md)
- [⚙️ Reliable](./how_rust_feels/reliable.md)
- [🐎 Performant](./how_rust_feels/performant.md)
- [🧩 Productive](./how_rust_feels/productive.md)
Expand Down
10 changes: 6 additions & 4 deletions src/what_is_this.md → src/goals.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
# Rustacean Principles

Rust is...
## What is Rust?

* a language empowering everyone to build reliable and efficient software that is meant to last;
* an open-source community focused on creating, designing, and maintaining that language and its ecosystem.
* A language empowering everyone to build reliable and efficient software that is meant to last.
* An open-source community focused on creating, designing, and maintaining that language and its ecosystem.

The **Rustacean principles** are a set of principles which guide us in achieving those goals.
## What are the Rustacean Principles?

The **Rustacean principles** are a set of principles which guide us in building Rust. They begin with a description of [how Rust ought to feel](./how_rust_feels.md) when you are using it. These goals guide us in designing features and help us decide how to

* [How Rust ought to feel](./how_rust_feels.md) covers the underlying design principles of Rust.
* [How to Rustacean](./how_to_rustacean.md) describes the way that Rust team members are expected to act. You can think of it like a companion to the [Code of Conduct][CoC]: whereas the [CoC] describes the bare minimum expected of any Rust participant, the [How to Rustacean] section describes what is takes to become a member of a Rust team.
Expand Down
4 changes: 2 additions & 2 deletions src/how_rust_feels.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ This section identifies the way that Rust ought to feel, when everything is goin

> The translation from Rust to underlying machine code is straightforward and predictable. If needed, you have options to control the low-level details of how your application works.
## [🥰 Accessible](./how_rust_feels/accessible.md): "build the system you want to build, whoever you are"
## [🥰 Supportive](./how_rust_feels/supportive.md): "build the system you want to build, whoever you are"

> Rust is meant to be used in practice. We pay a lot of attention to the details of things like error messages and our tooling workflows. Because being accessible ultimately requires more than technology, we work hard to have a community that is welcome and supportive to everyone -- not just people who already know what they are doing.
> We strive to make our tools polished and friendly, and we look for every opportunity to guide people towards success. Part of that is building a community that eagerly shares its knowledge in a welcoming and inclusive way.
## [🤸 Versatile](./how_rust_feels/versatile.md): "whatever it is I want to do, I can use Rust to do it"

Expand Down
3 changes: 0 additions & 3 deletions src/how_rust_feels/empowering.md

This file was deleted.

1 change: 0 additions & 1 deletion src/how_rust_feels/supported.md

This file was deleted.

0 comments on commit 3a9308b

Please sign in to comment.