arnodirlam
Hi!
I want to match an exception in a rescue block, matching it to several exception modules.
One of the modules is not defined (because I forgot an alias) but neither the compiler, dialyzer, nor credo emit a warning about it.
defmodule ErrorHandler do
alias Errors.A
alias Errors.B
def handle_errors(fun) do
fun.()
rescue
error in A ->
{:hard_failure, error}
error in B ->
{:outage, error}
# undefined/unaliased module C but no warning emitted
error in C ->
{:transient_error, error}
end
end
Is it possible to have a warning emitted in such cases somehow?
If not, what would be the best place to introduce a warning like this, if this makes sense at all?
Thanks in advance!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
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!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
Well, there could be a
Cdynamically loaded at runtime, so there is nothing the compiler could complain about.dogweather
Yeah, I found this behavior shocking when I learned about it. The bottom line seems to be that an original BEAM core design is to support a highly dynamic runtime environment; where code can be swapped in and out (“dynamically loaded”). And the issue is, we’re using this system for a whole new set of kinds of apps which are static in nature. E.g., a CRUD Phoenix web app probably is designed to work only with the modules packaged with it at deploy time. And a static code update is easy in the modern era when we can e.g. re-deploy instantly to Heroku without any downtime.
Personally, I’d appreciate a way to flag my app as “non-dynamic”, and then get linking errors at compilation time.
I bumped into your problem in a different context: I want compile errors from router.ex, but everything compiles fine. (?)
josevalim
I have posted this on another thread but, for completeness, if you don’t want your code to compile in those cases, you can enable warnings as errors:
Or if you want to enable it only for xref:
PS: @dogweather sorry that you are getting duplicate answers but since people may arrive here from Google, etc, I wanted to post an alternative to get an error on undefined modules.