Rich_Morin
I wonder if one of the Elixir tools can / should / already does have an option to report instances of non-tail-call recursion, in order to help developers notice this infelicity. AFAIK, the compiler already has to check for this; what about adding an option or perhaps an attribute to ask for reporting on this?
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #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.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
Body recursion is 100% appropriate in lots of circumstances. There are some technical issues with what you’re asking too but before we dive into that, can you elaborate more about the issue you’re trying to prevent?
Rich_Morin
After decades of dabbling in recursion, I’m only barely competent at writing code in that style. So, I generally make do with pipelines of calls to filter, map, reduce, etc. Even when I get some recursive code running, I may not be using a tail call.
However, if some program would tell me “this routine isn’t using a tail call”, I might be able to look over the code and fiddle with it until the program is happy. I could then decide whether I think the change improved things, from the standpoint of performance, readability, etc.
derek-zhou
Tail recursion is not always better than body recursion; and the difference is usually not that big anyway. For example in this case:
https://forum.elixirforum.com/t/picking-up-fp-coming-from-oop-split-thread/33187/96?u=derek-zhou
My advice are:
Rich_Morin
This advice seems very reasonable to me. Basically, the only time tail recursion is likely to make a substantial difference is when it’s being used in a processing-intensive “inner loop”.
Even then (as always), profiling is strongly advisable before attempting any code optimization. I’m also very much in agreement with trying to keep the code clear and idiomatic. So, I guess the take-away is “nothing to see here; move along …”.