Alastair Hole

I don't believe this is redundant, e.g.: ```javascript res = { body: {} } res.body && (res.body.message || res.body) //{} res = { body: { message: 'hello' } } res.body...

Thanks for such a detailed response, makes perfect sense. The `iam` modules look really useful, I am tempted to use them in place of my ad hoc assertions for `exp`...

Unfortunately I'm using Erlang 22 and getting `erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace` warnings with OJSON and IAM. Shall I open issues on those...

Ah yes of course - I had assumed they were causing problems but it must have been a red herring and just a problem with my attempt at translating the...

Just tried again and I'd forgotten that this is a compile failure (in erl 22/22.1 at least): ``` ===> Compiling _build/default/lib/ojson/src/ojson_decoder.erl failed _build/default/lib/ojson/src/ojson_decoder.erl:89: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax...

This seems to work for now in rebar3.config: ``` {overrides, [{override, ojson, [{erl_opts, [debug_info]}]}, {override, iam, [{erl_opts, [debug_info]}]}] }. ```

I believe it is a Rebar3/Relx feature: > Starting with Erlang/OTP 21 and rebar3 3.6.0 the configuration options sys_config_src and vm_args_src are available for explicitly including templates that will be...

I'm not sure how easy it would be to support, before substitution the files are not valid terms

Yeah maybe this is beyond the scope of a formatter, it's impossible to know even what the variables will expand to anyway

Doesn't work for me in Safari 10 on 10.11.6 either