Erlang style - case vs function pattern matching
I've got to the stage where I've written quite a bit of Erlang code now, and I can see some style (bad or good) creeping into the way I've been writing it. This particular idiom I'd like some opinion on - is it better (more readable/faster/whatever) to convert case style statements to function pattern matching? E.g. Compare (a contrived example) case {Size > 100000, Type} of {true, ets } -> %% Do
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
how to phoenix app with local path dependency to Heroku
Obtain rejected/unfiltered elements from Enum
Update Postgres table using Ecto/Elixir
Parameterised Modules in Erlang
Can a Dispatcher access it's parent Producer methods/attributes?
Remove key value pairs from a map dynamically
Is there any way to use shared examples in the ExUnit?
Erlang, Last Call Optimization, lambda functions, and how to prevent growing a stack
Iterating over list of tuples in elixir using Enum
How to switch layout by user agent
ETS does not seem to store my insert
Elixir online IDE/playground website
Can the port be specified for localhost using HTTPoison?
Erlang shell from a browser?
Handle views using Phoenix as a RESTful API app
Ex_machina changing data upon creation
ODBC link check failed error while compiling Erlang OTP on FreeBSD 10.1
Why does lists:flatten/2 does not work fine on Erlang script?
How can I remove elixir completly from Mac