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.

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

This PR fixes typos. #314

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

This PR fixes typos. #314

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
86f7df0
fix: typo
prokopschield Jan 23, 2025
d2cf623
fix: comma
prokopschield Jan 23, 2025
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 src/sixth-basics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ impl<T> LinkedList<T> {
}
```

PhantomData is a weird type with no fields so you just make one by, saying its type name. *shrug*
PhantomData is a weird type with no fields, so you just make one by saying its type name. *shrug*

```rust ,ignore
pub fn push_front(&mut self, elem: T) {
Expand Down Expand Up @@ -183,4 +183,4 @@ test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; fini

Hooray, we're perfect!

...Right?
...Right?
2 changes: 1 addition & 1 deletion src/sixth-variance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ This is extremely annoying for Exactly Me as a person who has spent a lot of tim

> Unlike `*mut T`, `NonNull<T>` was chosen to be covariant over `T`. This makes it possible to use `NonNull<T>` when building covariant types, but introduces the risk of unsoundness if used in a type that shouldn’t actually be covariant.

But hey, it's interface is built around `*mut T`, what's the deal! Is it just magic?! Let's look:
But hey, its interface is built around `*mut T`, what's the deal! Is it just magic?! Let's look:

```rust
pub struct NonNull<T> {
Expand Down