Mention type placeholders in the manual and tutorial #12891
Comments
|
The manual should have this, but I don't want to add it to the Guide. |
|
I want to do this, but I'm not sure where it fits in the Reference... |
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this issue
Feb 13, 2015
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Feb 15, 2015
matthiaskrgr
pushed a commit
to matthiaskrgr/rust
that referenced
this issue
Aug 2, 2022
Use large stack on expander thread I have verified that this fixes rust-lang#12884 for me. Hat tip to `@bjorn3` for identifying the cause of the issue.
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Jun 13, 2024
… r=Manishearth
Fix grammer for the Safety documentation check
The original message ("unsafe function's docs miss `# Safety` section") reads quite awkwardly. I've changed it to "unsafe function's docs are missing a `# Safety` section" to have it read better.
```
changelog: [`missing_headers`]: Tweak the grammar in the lint message
```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#12764 landed, but didn't include docs for the feature.
The manual and tutorial should mention it in the context of type inference, and give a proper explanation:
_in a type is a "type placeholder" and has the meaning "infer this type".Vec<_>are called "partial type hints" and are useful in combination with things likecollect()on iterators.The text was updated successfully, but these errors were encountered: