andrenth
Hello
I’ve done some Erlang a long time ago and now I’m returning to the platform via Elixir. One the few things syntax-wise that I feel is sub-optimal is how you call Erlang functions, i.e., :module.function(...). It just looks a bit odd to me, although I do understand why it is this way.
Wouldn’t it be cool if we could use the same transformation done in keyword lists ([{:foo => 1}] being the same as [foo: 1]) and call module:function(...) instead, just like in Erlang? 
Where Next?
Trending in Discussions
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
- #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
- #ai
- #blog-post
- #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.
Catch errors, track performance, monitor hosts and more.
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!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Qqwy
I have an alternative for you:
hauleth
The point is that the current syntax is in par with the whole rest of the language, as
Foo.bar()is the same as:'Elixir.Foo'.bar()(with exception for the aliases). So adding new call syntax would mean thatFoo:bar()also would became valid call. While this could simplify some things (it would provide difference between function call and map access) I think it would be too confusing, especially asfoo. bar()is valid syntax andfoo: bar()will not be.hauleth
Why and how would you do that in case of non-core modules? Like
poolboy?