Add print_err to Result

[leaty]

We have so many great functions to handle errors on a Result, but we have nothing to simply eprintln! it and go our merry way. Sometimes it's nice to always print the error (if any) without actually handling it.

This is one such example using channels for events:

tx.try_send(event)
	.inspect_err(|e| eprintln!("{e}"))
	.ok();

Could be just:

tx.try_send(event)
	.print_err()
	.ok();

I know it's not a huge deal, but the repetition of using the same exact format string every time got to me :)

[programmerjake]

imo rust should encourage using a logging library rather than making it overly easy to use eprintln for errors.

[leaty]

While I can see that being the case (easy to reach for a simple solution), it's also a big dependency for essentially no gain in many cases. Writing errors to stderr is not the same as logging errors with time and context (log to stderr or otherwise is irrelevant). It's great for sure, but not always necessary.

[scottmcm]

If you'd like to add a method like this, the current process is for you to open an ACP for the libs-api team to consider.

As such I'm going to close this issue, as the RFCs repo isn't the best place to discuss it.