Thanks for the feedback! Have you seen the “Server-Side Consistency Tests” section in the Contributing Guide? The idea is that you implement matching tests in Elixir (in test/elixir/hologram/ex_js_consistency/erlang/) that mirror your JavaScript tests. These verify your JS implementation behaves identically to the actual OTP implementation. And if OTP behavior changes in the future, it’ll be caught.
Does this resolve the issue for your :erlang.make_tuple/2 case, or should we make this clearer in the docs?
Also, could you elaborate on your term_to_binary idea? I’m curious what you have in mind.
