Viewing profile — osiris88

I don’t disagree with you but I disagree on a point of history. > Without the protections the Americans tried to shove into the First Amendment (which did not include anything abou…

In C++ it will throw an exception which you can catch, and then gracefully report that the operation exceeded limits and/or perform some fallback. Historically, a lot of C code fai…

Let me be clear cause I think my initial post was harsher sounding than I intended. I love working in rust. I love Result, and the ? sigil, etc. I love the enums and match, and how…

Yeah, the edition thing is cool, but there's also a cost to it, which is that over time you accumulate more and more support code in the compiler for really ancient editions. I don…

Let's continue discussion here: https://news.ycombinator.com/item?id=46416377 I think it's true that right up until 1.0, backtrace was a part of `trait Error`, then it was deprecat…

> I took it as a statement of fact. It is a factual matter of whether `std::error::Error` has a point to it or not. And it definitively does. I use the error chain in just about ev…

There's a semantics discussion about whether progressively adding context to errors (forming an error chain) counts as "error accumulation" or if error accumulation means collectin…

> I wrote about how to do error handling without libraries literally the day Rust 1.0 was published: https://burntsushi.net/rust-error-handling/ > > That blog did include a recomme…

By error accumulation, I mean a tree of errors, not a simple chain. The chain is only useful at the very lowest level. The tree allows you to say e.g. this function failed because …

OP is spot on, no deps is the way. I've been using rust for 8+ years, I remember the experiments around `failure` crate, a precursor to anyhow if I remember right... and then eyre,…

I used to develop free software exclusively under GPL or AGPL. But at some point, for things like, a very small-but-useful library or utility, I had a change of heart. I felt that …