hello-world.rs VS thiserror

Obligatory rust implementation.

Not mine but https://github.com/mTvare6/hello-world.rs

Yeah rust doesn't have any practical applications, it's mostly just a meme for aesthetically-motivated programmers who barely know what they're doing and want to make the most nonsense bloated soyware imaginable. See: https://github.com/mTvare6/hello-world.rs

https://github.com/mTvare6/hello-world.rs - 2,700 stars

> Somehow Rust forces you to have colorful terminal output? Rust is high overhead? You can't strive for simplicity and write in Rust?

This was more of a sarcastic reference to https://github.com/mTvare6/hello-world.rs

https://github.com/mTvare6/hello-world.rs (ok maybe this one is a bit too much lol)

Obligatory Rust (and Rocket-Ship emoji) implementation of Hello-World

We can utilize third-party libraries to simplify the code above. For example thiserror (https://github.com/dtolnay/thiserror) provides convenien derive macro for Error trait:

thiserror crate makes it easy to do so using macros on CliError enum.

Depending on your use case, thiserror and/or anyhow.

What is the benefit of splitting a proc-macro crate into (usually) two crates, proc_macro_crate and proc_macro_crate_impl? Why not just have one crate? Does it offer any benefits to to overall compilation times? An example of this can be seen in the thiserror crate where there's a thiserror and thiserror_impl crate.

You might want to use thiserror to generate implementation for Error and Display.

thiserror for my error types.

thiserror - https://crates.io/crates/thiserror

I dont think you realize how ridiculous this comment is. Youre comparing 10 lines of Go, with 200 of Rust:

https://github.com/dtolnay/thiserror/blob/master/src/lib.rs

There are crates out there that help you reduce this boiler plate. thiserror is good for creating custom errors and color-eyre or anyhow are good for dynamic errors.