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

Emoji based error handling #1565

Closed
wants to merge 1 commit into from
Closed

Conversation

dbrgn
Copy link

@dbrgn dbrgn commented Apr 1, 2016

Rendered

@dbrgn dbrgn changed the title New RFC: Emoji based error handling Emoji based error handling Apr 1, 2016
@ticki
Copy link
Contributor

ticki commented Apr 1, 2016

👍 ❤️ 🎉 :shipit: 🎱 💯 🔢 😄 🏆

@burdges
Copy link

burdges commented Apr 1, 2016

This RFC does not even display properly. lol

@dbrgn
Copy link
Author

dbrgn commented Apr 1, 2016

This RFC does not even display properly. lol

That is addressed in the "unresolved questions". Creating a custom Rust font and/or forking Servo or Firefox to build our own Rust browser with full Emoji support would trivially resolve that problem. 🍻

@gerryxiao
Copy link

It seems great for others also,not just for errors

@diwic
Copy link

diwic commented Apr 1, 2016

Why stop with error handling? Changing keywords would be even more interesting. With just a few ones exchanged, e g:

pub = 🍺 (well, you can do other things at the pub too)
fn = 😄 (fun!)
struct = 🏢 (a building!)
trait = :trollface: (clearly a traitor!)
mut = 🔇 (muted!)
derive = 🚗 (sitting in the front seat)

Example code:

#[ 🚗 ( De 🐛 )]
🍺 🏢 April1st {
fooled: bool
}

impl 💧 for April1st {
😄 💧 (& 🔇 self) {
println!("{:?}", self);
}
}

@bungcip
Copy link

bungcip commented Apr 1, 2016

Quick someone, please create rfc to use unicode character for lifetime!

fn foo(a: &str1) -> &str1

@birkenfeld
Copy link

If possible, consider compatibility with PEP 3117 for maximum synergy :)

@ticki
Copy link
Contributor

ticki commented Apr 1, 2016

We really need this for Redox, it makes everything much better.

@ghost
Copy link

ghost commented Apr 1, 2016

I'm glad the Rust team is trying to get ahead of the curve with error messages. After Microsoft replaced their old blue screen with the super useful ASCII sad face I finally realized that the computer's emotions tell me more than an error code ever could.

@lifthrasiir
Copy link
Contributor

As with other newly proposed features, we propose adding a feature gate for emojified error handling:

#[feature(emojification)]

Besides from a missing !, I believe this should read #![feature(🌅)] which signifies the bright new future of post-Emoji Rust.

```rust
enum 🙏<T, E> {
🍻<T>,
💩<E>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😱⚠️ These should be

enum 🙏<T, E> {
    🍻(T),
    💩(E), 
}

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😱!()

@ticki
Copy link
Contributor

ticki commented Apr 2, 2016

Can we close this as postponed? MIR is clearly blocking.

@burdges
Copy link

burdges commented Apr 4, 2016

We should ask this ISO Trump++ guy to weigh in here. Is he on github?

@nikomatsakis
Copy link
Contributor

After deep and thorough consideration, the @rust-lang/lang team has decided to close this RFC. It just doesn't quite fit into our priorities at this time. Maybe later!

@Centril Centril added the april-1st RFCs started on the 1st of april. label Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
april-1st RFCs started on the 1st of april.
Projects
None yet
Development

Successfully merging this pull request may close these issues.