frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
1003•pcompeau•8h ago•153 comments

Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use

https://xusheng.dev/posts/windows-coding-agent-telemetry/
380•cwaffles•5h ago•236 comments

BugMeNot has closed

https://www.bugmenot.com/
407•lode•7h ago•199 comments

Optimizely compromised, served malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
185•kristjansson•5h ago•93 comments

Running coding agents without handing them my credentials

https://blog.antonio.cx/running-agents-with-lend
65•antoniomika•3h ago•27 comments

If an App Asks for Full Disk Access or System and App Protection Override

https://support.apple.com/en-us/149699
47•jshier•2h ago•27 comments

OpenCode Browse

https://opencode.ai/product/browse
172•mfiguiere•7h ago•79 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
160•sebg•8h ago•79 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
343•geerlingguy•12h ago•241 comments

Mem Is Shutting Down

https://get.mem.ai/blog/mem-is-shutting-down
31•qainsights•2h ago•36 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
342•burntsushi•11h ago•78 comments

Why 3dfx 1 cards had such a washed out color output?

https://twitter.com/id_aa_carmack/status/2122478083319992513
39•mfiguiere•4h ago•0 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

35•arshpatankar•8h ago•13 comments

Formal Verification Is Not Verifiable

https://alperenkeles.com/posts/formal-verification-is-not-verifiable/
85•zdw•2d ago•26 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
244•PaulHoule•11h ago•237 comments

How to Break into Security, Ptacek Edition (2012)

https://krebsonsecurity.com/2012/06/how-to-break-into-security-ptacek-edition/
93•ronfriedhaber•6h ago•21 comments

Comcast's "fiber-powered Wi-Fi" is cable, AT&T says in false advertising case

https://arstechnica.com/tech-policy/2026/11/comcast-falsely-advertises-cable-internet-as-fiber-po...
92•jaredwiener•8h ago•72 comments

Spamhaus new email sender requirements in November

https://www.spamhaus.org/sender-guidelines/
81•computer23•7h ago•77 comments

Why did modems have speakers? (2019)

https://retrocomputing.stackexchange.com/questions/11765
13•Skyfall106•1d ago•7 comments

Do Repeat Yourself

https://arcentry.com/blog/do-repeat-yourself/
51•max_sendfeld•16h ago•18 comments

Technical issue at JPMorgan Chase triggers online banking delays for US banks

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
739•samk3nny•10h ago•614 comments

Atomic Nuked Veteran

https://www.armscontrolwonk.com/archive/201309/atomic-nuked-veteran/
33•hubraumhugo•22h ago•7 comments

Squircles

https://linebender.org/wiki/curves/squircle/
152•raphlinus•20h ago•45 comments

Show HN: Sutra-OS – A self-hosted ontology platform

https://github.com/0nelight/sutra-os
44•0nelight•5h ago•21 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
256•Bender•15h ago•184 comments

My Quest to push native Three.js quality match AAA Game Engines

https://ben3d.ca/blog/building-the-aaa-lighting-pipeline-in-threejs
115•bhouston•7h ago•45 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
219•speckx•8h ago•140 comments

United Airlines experiencing a widespread system outage, airline says

https://www.cnn.com/2026/11/16/us/united-airlines-outage
213•bearsyankees•6h ago•109 comments

Pentagon fails ninth straight audit despite progress in organizing finances

https://www.reuters.com/business/aerospace-defense/pentagon-fails-ninth-straight-audit-despite-pr...
77•petethomas•4h ago•22 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
111•maufl•11h ago•60 comments
Open in hackernews

Show HN: Stack Error – ergonomic error handling for Rust

https://github.com/gmcgoldr/stackerror
27•garrinm•1y ago
Stack Error reduces the up-front cost of designing an error handling solution for your project, so that you focus on writing great libraries and applications.

Stack Error has three goals:

1. Provide ergonomics similar to anyhow.

2. Create informative error messages that facilitate debugging.

3. Provide typed data that facilitates runtime error handling.

Comments

tevon•1y ago
This is awesome! Will give it a try in my next project.

How does it keep track of filename and line number in a compiled binary? I'm fairly new to rust libraries and this doesn't quite make sense to me. I know in JS you need a source-map for minification, how does this work for a compiled language?

fpoling•1y ago
Rust provides file!, line! and column! macros that expands into a compile-time constants that the compiler embeds then into the executable. This way no source map at runtime is necessary as the relevant errors are constructed from those constants.

Presumably StackError just uses those macros.

But for debugging a source map is still necessary and is a part of various debug formats.

rhabarba•1y ago
I still prefer the Anyhow solution, but I like the approach here.
IshKebab•1y ago
Isn't this strictly superior to Anyhow? What do you like more about Anyhow?
rhabarba•1y ago
I prefer Anyhow's non-intrusiveness: "Result" is still "Result" and all I need is a "?". I agree with Stack Error's documentation that Anyhow can't help with debugging that well, but it's "good enough" in my opinion.
IshKebab•1y ago
Result in `anyhow::Result` though. It's still a different type. Or do you literally mean you like that it is still spelt the same?

And I think you can still use `?` with this if you don't want to add any context... Not 100% sure on that though.

rhabarba•1y ago
Might as well be my limited understanding from what I can read behind the link, to be fair.
garrinm•1y ago
Anyhow still makes things easier for application development. The main drawback is that the resulting error type doesn't implement std::error::Error, so it's not suitable for library development (as pointed out in the anyhow documentation). Stack Error is a bit less ergonomic, but suitable for library development.
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/index.html

garrinm•1y ago
I played around a bit with SNAFU a couple of years ago, but I'm haven't worked deeply with the library so there might well be some features I'm not aware of.

I think SNAFU is more like a combination of anyhow and thiserror into a single crate, rather than Stack Error which leans more heavily into the "turnkey" error struct. Using the Whatever struct, you get some overlap with Stack Error features:

- Error message are co-located.

- Error type implement std::error::Error (suitable for library development).

- External errors can be wrapped and context can easily be added.

Where Stack Error differs:

- Error codes (and URIs) offer ability for runtime error handling without having to compare strings.

- Provides pseudo-stack by stacking messages.

Underlying this is an opinion I baked into Stack Error: error messages are for debugging, not for runtime error handling. Otherwise all your error strings effectively become part of your public interface since a downstream library can rely on them for error handling.

lilyball•1y ago
If the macros only exist to get file and line information, you could do the same thing by using `#[track_caller]` functions combined with `std::panic::Location` to get that same info. For example, `stack_err!` could be replaced with

  impl StackError {
      #[track_caller]
      fn new_location(msg: impl Display) -> Self {
          let loc = std::panic::Location::caller();
          Self::new(format!("{}:{} {msg}", loc.file(), loc.line()))
      }
  }
such that you call `.map_err(StackError::new_location("data is not a list of strings"))`. A macro is nice if you need to process format strings with arguments (though someone can call `StackError::new_location(format_args!(…))` if they want), but all of your examples show static strings so it's nice to avoid the error in that case.

The use of `std::panic::Location` also means instead of baking that into a format string you could also just have that be an extra field on the error, which would let you expose accessors for it, and you can then print them in your Debug/Display impls.

Speaking of, the Display impl really should not include its source. Standard handling for errors expects that an error prints just itself with Display because it's very common to recurse through sources and print those, so if Display prints the source too then you're duplicating output. Go ahead and print it on Debug though, that's nice for errors returned from `main()`.

garrinm•1y ago
Thanks for the insight, I wasn't aware of `track_caller`. I'll definitely be looking into this. I was scratching my head trying to figure out how to make file and line number usage consistent and customizable, this looks like the answer!

You're also right that this will pretty much eliminate the need for macros.

That's also a very key insight about Display vs. Debug printing. I'll be looking into that as well.

Thank you for the thoughtful reply.

DavidWilkinson•1y ago
Dei here, from the team behind Error Stack [1] (a similarly named existing, context-aware error-handling library for Rust that supports arbitrary attachments). How does Stack Error, here, compare?

[1]: https://crates.io/crates/error-stack