-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Clarify the English translation of ?Sized
#33747
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -47,14 +47,15 @@ pointers, can use this `impl`. | |
# ?Sized | ||
|
||
If you want to write a function that accepts a dynamically sized type, you | ||
can use the special bound, `?Sized`: | ||
can use the special bound syntax, `?Sized`: | ||
|
||
```rust | ||
struct Foo<T: ?Sized> { | ||
f: T, | ||
} | ||
``` | ||
|
||
This `?`, read as “T may be `Sized`”, means that this bound is special: it | ||
lets us match more kinds, not less. It’s almost like every `T` implicitly has | ||
`T: Sized`, and the `?` undoes this default. | ||
This `?Sized`, read as “T may or may not be `Sized`”, which allows us to match | ||
both sized and unsized types. All generic type parameters implicitly | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "which" should be removed from the first sentence. |
||
have the `Sized` bound, so the `?Sized` can be used to opt-out of the implicit | ||
bound. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I think this is still not quite right...
My understanding is that you should be able to remove the appositive (the part between the commas) and still have a valid sentence. So I think the word "which" here is extraneous.
I'd prefer if someone else could chime in here as well on the grammar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm horrible with grammar, so I'll defer.