frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Stephen Wolfram "Live CEOing" videos of Wolfram Language feature development

https://www.youtube.com/playlist?list=PLxn-kpJHbPx14mHrB5BlhImVOWo5Geg6f
1•alok-g•14m ago•0 comments

OpenRouter requests to MiniMax models may have been read

https://www.reddit.com/r/LocalLLaMA/comments/1y1we95/openrouter_requests_to_minimax_models_may_have/
1•ksec•15m ago•0 comments

AWS local emulator created by AI agents

https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/
1•wenbert•22m ago•0 comments

The quantum computing race is becoming a deployment race

https://www.techradar.com/pro/the-quantum-computing-race-is-becoming-a-deployment-race
2•jonbaer•29m ago•0 comments

'I was shaking, crying, having trouble breathing': the uncharted trauma

https://www.theguardian.com/technology/ng-interactive/2026/nov/21/shaking-crying-trouble-breathin...
1•user20180120•32m ago•1 comments

Show HN: The Riemann Proof Handbook

https://github.com/tamnd/riemann-handbook
2•tamnd•32m ago•0 comments

WikiLLM: Browse language model weights like an encyclopedia

https://github.com/eagleclaw0075/wikillm/
1•havemurci•35m ago•0 comments

Show HN: Npx.tools, a keyboard-friendly index of developer tools

https://npx.tools/
1•hasnainkhagan•39m ago•0 comments

AI as a Lifestyle Choice

https://grahamdumpleton.me/posts/2026/11/ai-as-a-lifestyle-choice/
1•Karrot_Kream•50m ago•0 comments

California Nvidia Probe Covers Potential Criminal Law Violations

https://www.bloomberg.com/news/articles/2026-11-21/california-nvidia-probe-covers-potential-crimi...
2•petethomas•53m ago•0 comments

Ask HN: What made you pivot your interest to the field of AI?

4•learner_yearner•59m ago•2 comments

The Explorer Pattern for product invention and development

https://lethain.com/explorer-pattern/
1•gpi•59m ago•0 comments

Replaced PTX with MLIR, cutting asm regions from 499 to 81 across 20 kernels

https://vxlang.org/blog/handing-the-ptx-back-to-the-compiler.html
4•reshabh•1h ago•1 comments

San Francisco Braces for Record Tides as Mayor Urges Residents to Stay Put

https://kfn.one/news/san-francisco-braces-for-record-tides-as-mayor-urges-1d795047
2•reena•1h ago•0 comments

Back Pain (2021)

https://www.thomas-huehn.com/back-pain/
1•Curiositry•1h ago•0 comments

AI Supply Chain Security: What Canary Tokens Found

https://www.dragos.com/blog/ai-supply-chain-security-canary-tokens
2•kristianp•1h ago•0 comments

Replaying an agent run and what it takes

https://github.com/chizy7/tether/blob/master/docs/REPLAY.md
3•chizy7•1h ago•0 comments

Trump threatens penalties for US tech firms that build datacenters abroad

https://www.theguardian.com/us-news/2026/nov/20/trump-datacenters-white-house
4•Pxtl•1h ago•1 comments

AiDotNet – Comprehensive AI/ML Framework for .NET

https://github.com/ooples/AiDotNet
2•olvy0•1h ago•0 comments

Why founders say launch directories send little traffic, and how they judge them

https://mambatxhub.com
1•aishabethuel127•1h ago•0 comments

Strangler pattern, a powerful simple concept to do refactoring (2019)

https://martinfowler.com/bliki/StranglerFigApplication.html
1•zenincognito•1h ago•0 comments

ING's $500M Data Center Loan Auction Stalls on Weak Demand

https://www.bloomberg.com/news/articles/2026-11-20/ing-s-500-million-data-center-loan-auction-sta...
1•cobychapple•1h ago•0 comments

Job ghosting: What applicants can do if employers do not respond

https://www.bbc.com/news/articles/cm2d94le23xyo
4•rustoo•1h ago•0 comments

Userscript managers in 2026: what Manifest V3 changed

https://www.softwr.com/news/best-userscript-managers
2•peter_d_sherman•1h ago•1 comments

"Dumbass" RFK Jr. Rescued Measles from Obscurity. What Horror Is Next?

https://newrepublic.com/post/218245/rfk-jr-measles-trump-outbreak
11•petethomas•1h ago•5 comments

What It Looks Like to Parent Without Gender

https://www.thenation.com/article/society/what-it-looks-like-to-parent-without-gender/
3•petethomas•1h ago•0 comments

One Vulnearbility Hacks Google, WordPress, Roundcube, Debian 13, Zoom, Box, etc.

https://pwn.ai/upload2shell/research.html
3•lovetoseeitgeth•1h ago•1 comments

A Collision for 38-Step SHA-256

https://eprint.iacr.org/2026/2913
1•gslin•1h ago•0 comments

NixOS bring-up on an Alibaba RISC-V board

https://feyor.sh/blog/nixos-bringup-on-an-alibaba-riscv-board/
2•todsacerdoti•1h ago•1 comments

Trump at the "Summit": One of His Dumbest Moments in the Last 10 Years

https://newrepublic.com/post/218235/trump-summit-xi-putin-nuclear
5•petethomas•1h ago•0 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