Re:Elixir for Ruby developers: the three most important diff...
by john_the_writer on Monday July 24, 2023 @08:21AM
(#36846772)
Mostly the dev cycle in Elixir is different. There are no "binding.pry". We're back to putting logs in the code.
[ Parent
| on HN ]
Re:Elixir for Ruby developers: the three most important diff...
by bobwaycott on Monday July 24, 2023 @09:16AM
(#36847491)
Use `dbg` for prying. You can also use `break!` in an `iex` session to manually set breakpoints without modifying your source. Additionally, you can use Erlang’s `:debugger`for visual debugging, and `:observer` for understanding the entire VM when prying is not enough.
Re:Elixir for Ruby developers: the three most important diff...
by quaunaut on Monday July 24, 2023 @11:11AM
(#36849285)
This is not nor has not ever been true.
Now, you've got `dbg()` and running whatever you're running via `iex -S <whateveryouweredoinghere>`.
Prior to `dbg()` you had `IEx.pry()`.
Re:Elixir for Ruby developers: the three most important diff...
by senjin on Monday July 24, 2023 @11:12AM
(#36849311)
`dbg` is relatively new but [IEx.pry](https://hexdocs.pm/iex/IEx.Pry.html) has been around for a long itme