"hello world" contains Lovecraft quotes

[pcwalton]

Yes, really

[alexcrichton]

It looks like this is 2640 bytes of lovecraft quotes in each exectuable (out of 469320, 0.56%). Perhaps it's not so bad?

[thestinger]

2k is pretty bad, because a hello world binary should be ~10k at most. It's not the lowest hanging fruit right now but it will become a bigger fish as we fix the other problems. I think it's an indication of a larger issue rather than being a problem itself though...

[pcwalton]

I think there is no defensible reason to have that text in every executable.

[nddrylliog]

And thus poetry was killed...

[bharrisau]

Not particularly new - 29ad8e1 and 51abdee

[adrientetar]

2K? So that's what 2014 is about?

[thestinger]

@adrientetar: If you want Rust to be taken seriously as a systems language, you have to worry about that. It's not acceptable in many embedded environments for binaries to be this large. It makes the language unusable without writing the entire standard library again. It's fine for it to be in the standard libraries... just not every binary linking against them.

[tbu-]

Should be fine until other sources of bloat are removed.

[thestinger]

The problem here isn't the quotes, it's that the code containing the quotes is used or considered used at all. It's the canary in the coal mine. I'm sure we can cut down the runtime overhead to something much smaller, including getting rid of this.

[rcxdude]

It's not unreasonable for it to be considered used, considering it's part of the abort code, so even a trivial program might trigger it (e.g. on OOM, stack corruption, etc). Personally I'd add a no_horrors cfg option or something to disable it in the rare cases where 2k is considered important, unless the potential for user confusion is considered to great to keep the behaviour at all.

[thestinger]

It's not rare for people to compare the size of the binaries to C and decide against using Rust for their use case due to it being very unfavourable. You shouldn't have to compile Rust again to disable debugging features useful only to the developers. This is only the runtime abort code, it's not the generic abort which isn't even a function call.

Runtime errors should report real errors, and logic errors should be dealt with by improving the code so redundant checks aren't necessary in the normal release builds. It can remain around in a build that's not for regular end users... the code paths calling this just need some work to remove the need for debugging stuff.

[steveklabnik]

Yeah but I love it though :( Hehe.

[bstrie]

I also love it, but it's more important to be professional and chuck it out. Let's not make this Rust's equivalent to T_PAAMAYIM_NEKUDOTAYIM. Easter eggs are fun, but they have to have literally zero impact on users.