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

fix: typos in documentation files #369

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
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
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ For example, a new change to the PARSER crate might have the following message:
// ================================================================================
```

- [Rustfmt](https://github.com/rust-lang/rustfmt) and [Clippy](https://github.com/rust-lang/rust-clippy) linting is included in CI pipeline. Anyways it's prefferable to run linting locally before push:
- [Rustfmt](https://github.com/rust-lang/rustfmt) and [Clippy](https://github.com/rust-lang/rust-clippy) linting is included in CI pipeline. Anyways it's preferable to run linting locally before push:
```
cargo fix --allow-staged --allow-dirty --all-targets --all-features; cargo fmt; cargo clippy --workspace --all-targets --all-features -- -D warnings
```
Expand Down Expand Up @@ -107,4 +107,4 @@ We use [semver](https://semver.org/) naming convention.
 

## Any contributions you make will be under the MIT Software License
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
2 changes: 1 addition & 1 deletion parser/src/sema/semantic_analysis.rs
Original file line number Diff line number Diff line change
Expand Up @@ -1333,7 +1333,7 @@ impl<'a> SemanticAnalysis<'a> {
}
}
// We take care to only allow constructing Call with a function identifier, but it
// is possible for someone to unintentionally set the callee to a binding identifer, which is
// is possible for someone to unintentionally set the callee to a binding identifier, which is
// a compiler internal error, hence the panic
id => panic!("invalid callee identifier, expected function id, got binding: {:#?}", id),
}
Expand Down
2 changes: 1 addition & 1 deletion parser/src/transforms/inlining.rs
Original file line number Diff line number Diff line change
Expand Up @@ -704,7 +704,7 @@ impl<'a> Inlining<'a> {
}
// If the current statement is a `let`-tree, we need to generate a new `let` at
// the bottom of the tree, which binds the result expression as the value of the
// generated `let`, and uses the accumualtor expression as the body
// generated `let`, and uses the accumulator expression as the body
Statement::Let(ref mut wrapper) => {
with_let_result(self, &mut wrapper.body, move |_, value| {
let value = core::mem::replace(
Expand Down
Loading