andrenth
Erlang function call syntax
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? 
Most Liked Responses
Qqwy
I have an alternative for you:
alias :module, as: Module
Module.function(...)
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 that Foo: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 as foo. bar() is valid syntax and foo: bar() will not be.
hauleth
Why and how would you do that in case of non-core modules? Like poolboy?
Popular in Discussions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
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.
Real-time error tracking, performance insights, and observability for devs.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"