thiserror VS example-electron-license-activation

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.

I’m currently developing a commercial product with Rust and I was wondering what the best way to distribute and sell licenses for it is. Should I use a third party like keygen or is there an easy way I could get started on implementing my own. I’m out of my depth when it comes to software licensing so I figure I should ask before assuming it’s a task I can take on myself.

have you checked https://keygen.sh/, yoyll get ideas there

Some sort of customer portal (or spreadsheet), where the customer can add, remove licences. After payment/confirmation you simply generate a json and encrypt with an async key. In your soft you read that as config file input, that will limit how many users can be created etc. keygen.sh or any other tool might also do it.