Hacker News Reader

Value type exceptions went nowhere, because that was yet another paper that was never turned into a proper proposal.

Additionally, Khalil Estell has made an excellent work proving that the way exceptions are currently implemented is not optimal and there is plenty of room for improvement, when someone cares about their implementation.

"Cutting C++ Exception Time by +90%? - Khalil Estell - CppCon 2025"

https://www.youtube.com/watch?v=wNPfs8aQ4oo

View on HN

I created the D version of the value type exceptions proposal.

In the end, it was DOA due to compiler architecture, so that was the end of that beautiful design.

I've had to accept result types is about as good as its going to get, all that is missing to make them nice is unwrapping support in if statements. Which I too have a proposal for and implemented it. But alas politics.

You might not see this since I'm rather late. What is a value type exception? Is it one that doesn't collect a stack trace? Or doesn't unwind in the usual way or something?

Reply on news.ycombinator.com