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

Clarify documentation on std::io::read_line #38888

Closed
d33tah opened this issue Jan 6, 2017 · 2 comments
Closed

Clarify documentation on std::io::read_line #38888

d33tah opened this issue Jan 6, 2017 · 2 comments
Assignees
@frewsxcv
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools P-high High priority

Comments

@d33tah
Copy link

d33tah commented Jan 6, 2017

Take a look at this SO answer and the comments:

http://stackoverflow.com/a/41210857/1091116
@sanxiyn sanxiyn added the A-docs label Feb 14, 2017
@steveklabnik steveklabnik added A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools and removed A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools labels Mar 10, 2017
@frewsxcv frewsxcv self-assigned this Mar 15, 2017
@steveklabnik steveklabnik added the P-high High priority label Mar 15, 2017
@steveklabnik
Copy link
Member

tagging p-high, @frewsxcv is gonna take this one. Not a big thing, but we'll knock it out soon.

@frewsxcv
Copy link
Member

This seems to be already addressed in #36851. I also opened #40642 that should clarify the behaviors of these BufRead methods. So I think this can be considered done unless anyone else has an action item here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frewsxcv frewsxcv

Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools P-high High priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@steveklabnik @sanxiyn @d33tah @frewsxcv