Susumu Yamazaki

Of course! Thank you for your information

I'll change the specification of ZEAM IR according to IR or ASTs using tuples and lists. However, it's troublesome so I'll implement #71, change the specification of ZEAM IR, and...

Single-map version: ```elixir %{ global_vars: %{ fail: {:fail, [type: ["const", "int"]], 0} }, macros: %{ loop_vectorization: 4 }, nif_vars: %{ env: {:env, [type: "ERL_NIF_ENV"], nil}, argc: {:argc, [type: "int"], nil},...

It needs to replace some maps into keyword lists because the order of them is important. ```elixir %{ global_vars: [ fail: {:fail, [type: ["const", "int"]], 0} ], macros: [ loop_vectorization:...

I believe that will be useful to support `mix upload.hotswap`.

In case that NIFs exist but `mix upload.hotswap` is newer than them, Pelemay should give up to load NIFs and fallback to execute the user code by Elixir.

This issue is related to #156

Sorry, in Japanese.(I explained at Nerves JP Slack) Pelemayの仕組みを説明すると，次のような感じです。 1. defpelemay do … end の区間のASTをPelemayマクロが受け取る 2. 関数ごとに解析してCコードを `Application.app_dir(:pelemay, "src")`に生成する 3. Makefileを `Applicatoin.app_dir(:pelemay, "build")` に生成してビルドする。生成したNIFライブラリは `Application.app_dir(:pelemay, "priv")`に生成される 4. スタブElixirコードを `Application.app_dir(:pelemay, "priv")`に生成する。このコードをロードすると...

I recieved some comments and questions on the scope of the target. Thank you! The target architectures are supported architecture of Erlang and Clang. I got Erlang supports architectures according...

I'd also discuss candidates of supported architectures with YOU. If you ask us to support some architectures, we'd like to try to do so.