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

Jump to bottom

be vague about tuple size #17241

Closed
wants to merge 1 commit into from
Closed

be vague about tuple size #17241

wants to merge 1 commit into from

Conversation

steveklabnik
Copy link
Member

Fixes #17222

@huonw
Copy link
Member

huonw commented Sep 14, 2014

Would it be possible for you to cherrypick the commits from this, #17240, #17239, #17238 and #17237 into a single PR? (The bors queue is relatively long, so there's no point doing 5 tiny doc-only builds. :) )

r=me with that and my comment on #17240.

steveklabnik referenced this pull request in steveklabnik/rust Sep 15, 2014
@steveklabnik
remove rendundant function
51b4c51 
Fixes rust-lang#17230.
@steveklabnik steveklabnik deleted the twoples branch October 25, 2017 18:26
lnicola pushed a commit to lnicola/rust that referenced this pull request May 19, 2024
@bors
Auto merge of rust-lang#17241 - blyxyas:fix-typos, r=lnicola
65dbe8e 
Chore: Fix some typos

rust-lang#124948

> In RA we gladly take typo fixes, but for now we definitely want them in the upstream repository.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Guide: implies tuples have (only) two elements
2 participants
@steveklabnik @huonw