LostKobrakai
I’m in the process of working on a library, where I want to have quite expressive exceptions (due to a lot of domain specific constraints). I’m wondering if there any guidelines of how to best format those though?
There are questions like:
-
Are multi line exceptions generally fine?
-
When to start using blame if the stacktrace or expensive operations are not needed?
-
Is it generally ok to add ANSI escape sequences for formatting, or would this cause issues?
I noticed that e.g. the FunctionClauseError exception doesn’t add ANSI sequences by itself, but it’s special cased within IEx to add some proper coloring, while for other exceptions there’s a check for a reset sequence in the exception string.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #elixirconf-us
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
What do you mean by expressive exceptions? Is there any required format, or in general, a bucket list of requirements?
To me multi-line exceptions are always fine; you either need a stack trace or sometimes the error message cannot be super short. Both things shouldn’t ever be a deal-breaker when constructing exceptions / errors.
Another example: when showing errors in tests I love the “expected X, got Y” format.
I am definitely not an authority on anything (it’s questionable if I’ll be working commercial programming 10 years from now even) but I have found the following format successful when I was working on and with huge Java monstrosities a lifetime ago:
LostKobrakai
Not specifically, but I was experimenting with e.g. visualizing how a given input string doesn’t fit the things like expected lengths over just showing some abstract numbers.