# Extremely pre-RFC: \`eprintln!\`

**URL:** <https://internals.rust-lang.org/t/extremely-pre-rfc-eprintln/4635>\
**Category:** language design\
**Created:** [January 20, 2017, 5:28pm UTC](https://internals.rust-lang.org/t/extremely-pre-rfc-eprintln/4635 "2017-01-20T17:28:42Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![milesrout](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/milesrout/32/383_2.png) [@milesrout](https://internals.rust-lang.org/u/milesrout)\
**Post date:** [January 22, 2017, 10:54pm UTC](https://internals.rust-lang.org/t/extremely-pre-rfc-eprintln/4635/10 "2017-01-22T22:54:19Z")

</div>

I wonder if this is necessary. Maybe more convenient logging is really what people want and/or need. Being able to just write:

```
error!("Your disk {} is fscked.", disk_name);

```

without adding any libraries or importing anything or having to do anything beyond just typing that would be the correct solution. I think the only reason `eprintln!` would be useful is for short quick programmes where you just want to write a quick script to do something and don’t want to go to all the trouble of finding out that there’s a `log` crate, adding dependencies, downloading crates, adding `extern crate` etc.

---

_[View the full topic](https://internals.rust-lang.org/t/extremely-pre-rfc-eprintln/4635)._