José Valim 75541cf472 Condititionally compile and lazily compute __STACKTRACE__ (#7648) ...

Erlang/OTP 20 warns if the stacktrace is read outside of a
catch/rescue. This commit mirrors this behaviour by consistently
warning on `System.stacktrace/0` being used outside of a
catch/rescue.

Erlang/OTP 21 warns whenever System.stacktrace/:erlang.get_stacktrace
are used. Therefore we need to promote the usage of `__STACKTRACE__`
and make sure to conditionally compile it according to the OTP version.
This requires changes to the Exception normalization mechanism
so we compute `__STACKTRACE__` only when strictly required.

In future Elixir releases, `System.stacktrace/0` will warn when
used even inside catch/rescue.

2018-05-07 15:33:36 +02:00

..

eex

Restrict next break fits and eols on operators and function calls

2017-10-27 12:34:09 +02:00

fixtures

Move all code to erlang style apps

2012-07-05 20:20:16 +02:00

eex_test.exs

Condititionally compile and lazily compute __STACKTRACE__ (#7648)

2018-05-07 15:33:36 +02:00

test_helper.exs

Run the code formatter on test_helper.exs (#6671)

2017-10-09 13:56:40 +02:00