Closed
Description
Tracking issue for for rust-lang/rfcs#1869
@zackw would you be interested in sending a PR?
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Tracking issue for for rust-lang/rfcs#1869
@zackw would you be interested in sending a PR?
Activity
eprint(ln)!
rust-lang/rfcs#1869zackw commentedon Mar 14, 2017
>.>
Reopen #39229 and proceed from there?alexcrichton commentedon Mar 14, 2017
Sure yeah, want to resubmit that as a new PR?
zackw commentedon Mar 14, 2017
Is it actually necessary to resubmit? Couldn't you just reopen the existing one?
alexcrichton commentedon Mar 14, 2017
Let's stick with a new PR, easier on bors in general
steveklabnik commentedon Mar 14, 2017
@zackw when you make your new PR, mind also adding an entry to https://github.com/rust-lang/rust/tree/master/src/doc/unstable-book ? It doesn't need to actually have docs in it. Check out any of the chapters for the little template.
eprint!
andeprintln!
macros to the prelude. #39229eprint!
andeprintln!
macros to the prelude. #41192Rollup merge of rust-lang#41192 - zackw:eprintln, r=alexcrichton
Rollup merge of rust-lang#41192 - zackw:eprintln, r=alexcrichton
Mark-Simulacrum commentedon Jul 27, 2017
I think this was stabilized, though I don't see any discussion here. @alexcrichton Any idea where that happened? Closing anyway..
zackw commentedon Jul 27, 2017
For the record, the code change was merged in #41192.
alexcrichton commentedon Jul 27, 2017
Ah yes macros IIRC can't be stabilized in the same way as other items, so we added these as insta-stable.