Crosscut

Daily Thought - 2025-04-12

Hey, I'm Hanno! These are my daily thoughts on Crosscut, the programming language I'm creating. If you have any questions, comments, or feedback, please get in touch!

I see problems with error handling in Rust, and I'd like to improve on those with Crosscut. Less boilerplate code would be great. But more importantly, I want to make it obvious which errors can occur in a given program, and where.

This means, if I look at the main function of my program, I want its signature to show me all of the errors that could arise in the whole program. If I look at any function that's applied within the main function, I want to see which errors could originate from that function specifically. And so on, recursively.

This means that if a function can return an error, that specific error would need to show up in its signature. If a function called multiple others that return various errors, the union of all these errors would need to be visible in that function's signature. Tomorrow, I'd like to present a straight-forward way to achieve this, that might or might not fit the constraints of Crosscut.

Hey, you! Want to subscribe to my daily thoughts? Just let me know (maybe include a nice message, if you're up for it), and I'll send you an email every time I post a new one.