You can use reraise/3. It is a bit misnamed, but it is correct. But this
behaviour in particular sounds like a bug in the editor itself, given it
does have a line in the stacktrace specific to that file.
On Fri, May 15, 2020 at 8:04 PM Dallin Osmun wrote:
> I must be missing something. I am
I must be missing something. I am already using Macro.Env.stacktrace when
emitting my warnings and that's working great. The problem happens when
calling raise. Is there a way to pass a new stacktrace into raise? The docs
for Kernel.raise say it accepts either a message or an exception and
