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.

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

Draft changes for eprintln. #615

Closed
wants to merge 1 commit into from
Closed

Conversation

zackw
Copy link

@zackw zackw commented Apr 10, 2017

Here are draft changes to the second edition for eprintln!. This unfortunately touches a number of chapters that are close to being finalized, but I think it's important to mention this early on.

I forked for this quite a while ago, apologies for the potentially messy merge.

@carols10cents
Copy link
Member

Thank you!!!! ❤️ We'll review and incorporate this soon.

frewsxcv added a commit to frewsxcv/rust that referenced this pull request May 11, 2017
Add `eprint!` and `eprintln!` macros to the prelude.

These are exactly the same as `print!` and `println!` except that they write to stderr instead of stdout.  Issues rust-lang#39228 and rust-lang#40528; previous PR rust-lang#39229; accepted RFC rust-lang/rfcs#1869; proposed revision to The Book rust-lang/book#615.

I have _not_ revised this any since the original submission; I will do that later this week.  I wanted to get this PR in place since it's been quite a while since the RFC was merged.

Known outstanding review comments:

* [x] @steveklabnik requested a new chapter for the unstable version of The Book -- please see if the proposed revisions to the second edition cover it.
* [x] @nodakai asked if it were possible to merge the internal methods `_print` and `_eprint` - not completely, since they both refer to different internal globals which we don't want to expose, but I will see if some duplication can be factored out.

Please let me know if I missed anything.
frewsxcv added a commit to frewsxcv/rust that referenced this pull request May 11, 2017
Add `eprint!` and `eprintln!` macros to the prelude.

These are exactly the same as `print!` and `println!` except that they write to stderr instead of stdout.  Issues rust-lang#39228 and rust-lang#40528; previous PR rust-lang#39229; accepted RFC rust-lang/rfcs#1869; proposed revision to The Book rust-lang/book#615.

I have _not_ revised this any since the original submission; I will do that later this week.  I wanted to get this PR in place since it's been quite a while since the RFC was merged.

Known outstanding review comments:

* [x] @steveklabnik requested a new chapter for the unstable version of The Book -- please see if the proposed revisions to the second edition cover it.
* [x] @nodakai asked if it were possible to merge the internal methods `_print` and `_eprint` - not completely, since they both refer to different internal globals which we don't want to expose, but I will see if some duplication can be factored out.

Please let me know if I missed anything.
@steveklabnik
Copy link
Member

I would still like to see this land, but by now it's out of date 😦

@carols10cents
Copy link
Member

Since eprintln! is about to be stable next week, and since I had chapter 12 edits from nostarch to incorporate anyway, and since this PR has gotten out of date, I took the opportunity to incorporate eprintln! into chapter 12.

This PR also has a lot of changes that don't have anything to do with eprintln!. So I'm going to close this, please open new issues/PRs if there are specific changes you'd like to re-propose.

Thank you though! 🌴 🦀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants