> > I believe this information best comes from runtime... Generating a graph > could be useful but I don't see how it would be superior in anyway to > observer. >
Yeah, definitely don't want to reinvent observer, just have a mind map graph of the key runtime elements as a canonical reference available outside of runtime. Maybe I'll explore starting, interacting with, snapshotting, and graphing observer from inside a mix task, instead. That'd be nice and outside of core, although the exact opposite of the run-on-compiled-BEAM-code approach. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/24a92d32-3632-42ec-ab9b-a23e57a7351b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
