xpg
I generally enable warnings_as_errors in order to have the compiler fail hard in situations like invoking non-existing remote functions.
This worked well, until I started using @deprecated. As far as I see it, I now have to choose between the following two:
- Keep warnings as errors, and accept that
@deprecatedwill cause compilation errors. - Treat warnings as warnings, meaning that
@deprecatedwill only be a warning. But so will invocations of non-existing functions.
Is there a middle-ground I am missing? Where I can have warnings for deprecations, but errors for invoking non-existing remote functions.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
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
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #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!
Master modern tools, write cleaner code, and tackle real-world challenges.
**Building the future of software with AI, trust, and human connection.**
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)
LostKobrakai
The middleground is soft deprecation using
@doc deprecated: "…", but I’m not sure you’ll see those when compiling.xpg
That will do it, thanks.
It would be nice to be able to differentiate between warnings (unused variables vs. invoking non-existing remote functions, for instance). But I guess that will open a can of worms and/or a substantial set of compiler options (which wouldn’t really make anyones life easier)