Hello! I’ve been super impressed with the community here on the forum. Thanks for the help everyone has provided thus far! I just finished my first side project in Elixir and there are a couple of things I’m missing from ruby-land, and some minor annoyances I’ve run into. I’m guessing there are ext…

[image] mike_bianco: Automatically open up a REPL when an exception is thrown. In ruby, this is done via pry-rescue . Super helpful for quickly diving into the exact context where the error occurs. Not possible as in most cases the failed process do not exist (unhandled exceptions will kill c…

[image] hauleth: As well I doubt that it would be possible, as Erlang do not provide anything like Kernel#local_variables in Ruby. There’s Kernel.binding/1: Kernel — Elixir v1.20.2

Unfortunately it is macro, so it will not work in exception handling.

[image] hauleth: so it will not work in exception handling. Huh? iex(1)> a = 42 42 iex(2)> try do ...(2)> throw :ack ...(2)> catch v -> ...(2)> b = 6.28 ...(2)> IO.inspect(binding(), label: :Bindings) ...(2)> end Bindings: [a: 42, b: 6.28, v: :ack] [a: 42, b: 6.28, v: :ack] If a bind…

[image] hauleth: There was mix console but it was removed Thanks for this tip! Do you happen to remember what version this was in? I spot checked a couple of versions through 1.3 and didn’t see anything. [image] OvermindDL1: If a binding ‘can’ be used in the local scope, then binding() w…

[image] mike_bianco: Ah! Interesting. Is it possible to retrieve a context for the binding call from System.stacktrace ? If so, then we could plug it (ha! no pun intended!) into the Plug.Debugger to retrieve bindings for each level of the stack trace. That information is already available at …

Yeah, but in general you cannot do: def call(conn, opts) do a = 10 throw :ack end try do call(conn, []) catch v -> IO.inspect(binding(__STACKTRACE__)) # or other magic there end And get value of a. And that is what would be needed for what @mike_bianco want.

[image] hauleth: And get value of a . And that is what would be needed for what @mike_bianco want. What a? There is no a in scope at the point binding is called? Is there supposed to be an a?

In debuggers for many languages it’s possible to “break on exception” where the debugger would attach immediately where an exception happened (not anywhere higher up the stack). This is similar to what Ruby’s pry-rescue does and this is what @mike_bianco wants. I’m not sure if it’s doable on the BE…

[image] michallepicki: This is similar to what Ruby’s pry-rescue does and this is what @mike_bianco wants. Exactly. It’s an incredibly helpful debugging tool in ruby, and I would love to see something like this on the elixir side!

Help an Elixir beginner find missing development tooling!

Questions & Help Questions

OvermindDL1 August 13, 2019, 5:25pm 8

That information is already available at compile time via macro’s, so a macro can already access that information.

Hmm?