Skip to content

feat(part-5-intro): make "Part 5" obvious #1753

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Aug 11, 2023
Merged

feat(part-5-intro): make "Part 5" obvious #1753

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
4806958
feat(part-5-intro): make "Part 5" obvious
ismailarilik Jul 25, 2023
2f0aa1e
fix(part-2-intro): remove the phrase "from Part 1" which is not exist
ismailarilik Aug 7, 2023
72e2467
revert(part-2-intro): revert 2f0aa1e
ismailarilik Aug 11, 2023
20de5ac
revert(part-5-intro): revert 4806958
ismailarilik Aug 11, 2023
0e6116b
refactor(parts): remove part numbers to be consistent
ismailarilik Aug 11, 2023
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
2 changes: 1 addition & 1 deletion src/part-2-intro.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ end-to-end process of compilation _and_ readers interested in learning about a
specific system they wish to contribute to. If anything is unclear, feel free
to file an issue on the [rustc-dev-guide
repo](https://github.com/rust-lang/rustc-dev-guide/issues) or contact the compiler
team, as detailed in [this chapter](./compiler-team.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would not have reverted this

team, as detailed in [this chapter from Part 1](./compiler-team.md).

In this part, we will look at the high-level architecture of the compiler. In
particular, we will look at three overarching design choices that impact the
Expand Down