Viewing profile — shepmaster

You can thank ASCIIFlow for that ;) https://asciiflow.com/

> Haven't used --update-refs, but reading it, it should result in your third graph. I don't think it does. I tried locally: mkdir test; cd test; git init touch a; git add a; git co…

I'm not sure that answers my question. That shows a linear set of branches (my-feature-v3 depends on my-feature-v2 depends on my-feature-v1 depends on main). I'm asking about the c…

Ah, good catch. That's more of a graphic issue and not what I was trying to express. Updated the OP.

> That last part goes further than git rebase --update-refs, which only moves refs sitting inside the range you’re actively rebasing. git history instead finds and rewrites every l…

At a Pittsburgher, I assumed it was a misspelling of “nebby”. https://www.urbandictionary.com/define.php?term=Nebby

> But it's not natural to do so. I tend to write most of my async Rust following the actor model and I find it natural. Alice Rhyl, a prominent Tokio contributor, has written about…

An official post about this is at https://blog.rust-lang.org/2025/09/12/crates-io-phishing-cam...

You are quite welcome; thanks for the kind words!

You certainly can use thiserror to accomplish the same goals! However, your example does a little subtle slight-of-hand that you probably didn't mean to and leaves off the enum nam…

In addition to the sibling comment mentioning thiserror, I also submit my crate SNAFU (linked in my ancestor comment). Reducing some of the boilerplate is a big reason I enjoy usin…

> I create one error type per function/action I do too! I've been debating whether I should update SNAFU's philosophy page [1] to mention this explicitly, and I think your comment …

Thanks for using SNAFU! Any feedback you'd like to share?

As we all know, Cool URIs don't change [1]. I greatly appreciate the care taken to keep these Compiler Explorer links working as long as possible. The Rust playground uses GitHub G…

I hope to read through your crate and examples later, but if you have a chance, I’d be curious to hear your take on how Stack Error differs from my library, SNAFU [1]! [1]: https:/…

SNAFU author here, thanks for including my crate! I’ll try to give your review a thorough read through later and incorporate feedback that makes sense. I do have https://diataxis.f…

I agree. Unfortunately, I think that a lot of the people who ask for a bigger standard library really just want (a) someone else to do the work (b) someone they can trust. The peop…

I agree with your general point, but for this specific functionality, I’ll point out that setting environment variables of the current process is unsafe. It took us a long time to …

Yeah, with SNAFU I try to encourage people going all-in on very fine-grained error types. I love it (unsurprisingly).

> [Rust and C++] encourages creating a library of types with inheritance You'll want to expand on and clarify your meaning here, as Rust does not have inheritance.

Yep, as the sibling said, it’s to prove the point in a snarky manner. The yellow-on-white color, the wobbling, upside down path of text, the font choice, the unrelated image; all o…

We made this to be used as a reply when pictures are misused where text would be better: https://fewer.pics/

Agree with simonw’s sibling comment. To add to it, I’m the primary maintainer of the Rust playground and basically self-review every single commit. The rust-lang/rust repository ha…