Oh, this thread is a year old, haha. Someone had just linked me to it.
tristan
Rebar3 Core Team
PragTob
Still good news and worth adding here if people find it through Google or what not. Thanks for chiming in I might try again with benchee 
3
kip
ex_cldr Core Team
Building on this thread I’d like to make some of my CLDR libs more easily consumable by erlang and lfe. As I read it the rebar3 plugin rebar_mix should take care of the compile phase for erlang. But the module naming is a little bit jarring on the other side. I am very comfortable using erlang modules in Elixir-land but I’m not sure that the reverse is true for erlangers..
For the erlangers here, what would you advise? Shim the Elixir modules with erlang style module names? No change and just suggest people get over it? Any other ideas?
1
ntalfer
In Erlang, module names must be atoms. For simplicity, to avoid the simple quotes, the common way is to use a module name with lower case characters, underscores and numbers only. The same thing is true for record names.
I understand it might be boring typing 'Elixir.X.Y':some_fun() from erlang source code, especially it there are many calls.
If someone’s not happy with that, there’s a quite simple solution which consists in adding a define for the module name and use it.
-define(LIB, 'Elixir.X.Y').
and perform calls like this:
?LIB:some_fun(),
?LIB:some_other_fun(),
2
toraritte
Apologies for the necrobump, but came across the Adopting Erlang online book, and there is a specific section in there about this topic (Development > Dependencies > Using Elixir Dependencies) that walks the reader through how to set up rebar_mix in Rebar3 projects to pull in Elixir hex.pm packages into Erlang applications.
8