shepmaster

5 ms·

1.
by shepmaster 16d ago
> What makes you think that? Here's a leaked / rumor image of Apple servers themselves. https://www.macrumors.com/2026/08/26/leaked-images-of-apple-...
2.
by shepmaster 2mo ago
You can thank ASCIIFlow for that ;) https://asciiflow.com/
3.
by shepmaster 2mo ago
> 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 commit -m 'a' touch b; git add
4.
by shepmaster 2mo ago
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 case where two or more branches fork from a commo
5.
by shepmaster 2mo ago
Ah, good catch. That's more of a graphic issue and not what I was trying to express. Updated the OP.
6.
by shepmaster 2mo ago
> 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 local branch descended from the commit (while also having
7.
by shepmaster 4mo ago
At a Pittsburgher, I assumed it was a misspelling of “nebby”. https://www.urbandictionary.com/define.php?term=Nebby
8.
Why Castrol Honda Superbike crashes on (most) modern systems(seri.tools)
176 points by shepmaster 10mo ago|35 comments
9.
by shepmaster 11mo ago
> 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 the specific patterns: https://ryhl.io&#
10.
by shepmaster 1y ago
An official post about this is at https://blog.rust-lang.org/2025/09/12/crates-io-phishing-cam...
11.
by shepmaster 1y ago
You are quite welcome; thanks for the kind words!
12.
by shepmaster 1y ago
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 name (or the `use` statement): low_level_result.cont
13.
by shepmaster 1y ago
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 using it.
14.
by shepmaster 1y ago
> 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 is the one that put me over the edge for &
15.
by shepmaster 1y ago
Thanks for using SNAFU! Any feedback you'd like to share?
16.
Parking_lot: Ffffffffffffffff(fly.io)
7 points by shepmaster 1y ago|3 comments
17.
by shepmaster 1y ago
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 Gists as the primary storage location for shared data. I
18.
by shepmaster 1y ago
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://docs.rs/snafu/latest/snafu/i
19.
by shepmaster 1y ago
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.fr/ and related stuff open in another tab an
20.
by shepmaster 1y ago
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 people working on Rust are a finite (probably overextended!) set
21.
by shepmaster 1y ago
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 realize it so the function wasn’t actually marked as unsafe
22.
by shepmaster 1y ago
Yeah, with SNAFU I try to encourage people going all-in on very fine-grained error types. I love it (unsurprisingly).
23.
by shepmaster 1y ago
> [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.
24.
by shepmaster 1y ago
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 of these serve to make the concept actively hard to process.
25.
by shepmaster 1y ago
We made this to be used as a reply when pictures are misused where text would be better: https://fewer.pics/
26.
by shepmaster 1y ago
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 has higher scrutiny (in part driven by tools like bors, t
27.
by shepmaster 1y ago
That is a use of https://en.wikipedia.org/wiki/Weathering_steel , actually!
28.
Torvalds: You can avoid Rust as a C maintainer, but you can't interfere with it(arstechnica.com)
203 points by shepmaster 2y ago|188 comments
29.
by shepmaster 2y ago
Discussed three days ago: - https://news.ycombinator.com/item?id=43089468
30.
by shepmaster 2y ago
This is one of the things I like about SNAFU: it makes this preferred pattern the default and makes it nicer to use. For example, your usage would look something like this with SNAFU: create_dir(path).context(CreateStagingDirectorySna

More ›