News for hackers. Stuff that matters.

A comment on Migrating from Go to Rust. Parent comment

Re:Migrating from Go to Rust by dwattttt on Monday May 25, 2026 @01:34AM (#48263717)
I have tried to figure out some kind of unification between "collecting error state in a function", "logging error state", and "return error state to a parent".

I haven't found any satisfying solution to it all; collecting information for logging vs information that a caller would want... I've been meaning to investigate tracing_error to see if it brings it all together.

[ Parent | on HN ]
Re:Migrating from Go to Rust by awesome_dude on Monday May 25, 2026 @01:42AM (#48263754)
Regardless of language - if you find a good, clear answer - blog the hang out of it - I for one have been searching for the right way to manage this, and it's not (yet) clearer - other than what I've said so far
[ Parent | on HN ]
Re:Migrating from Go to Rust by iknowstuff on Tuesday May 26, 2026 @09:57AM (#48279975)
tracing_error is a nice option if you already have the tracing context.

snafu makes it easy to attach structured context to an error

[ Parent | on HN ]