3 ms·
A lot of that is by design. It's my understanding that they made the decision not to wrap erlang standard libraries just for the sake of wrapping them, because
by adamkittelson 12y ago
A lot of that is by design. It's my understanding that they made the decision not to wrap erlang standard libraries just for the sake of wrapping them, because the erlang standard libaries work just fine when called from elixir.
If something needed to be wrapped to make it play more nicely with elixir, for example to change argument order to better suit elixir's |> operator, or if there were other real benefits to wrapping an erlang library, then they might wrap it. Otherwise if the erlang library is good just use the erlang library.
- bphogan 12y agoYea, that's what I figured. But I don't like it so much. I tend to end up wrapping it myself just because I like piping with |>. But my main point was that when I started, I could just look to one source for language docs. But as I dug in, I realized that to do a lot of things, I needed to look at Erlang too. And then I realized I had to understand it. It's not bad, it's just a thing that makes learning the awesome language a lot more difficult.