> > The issue here is that internal implementation of my custom guard and even > built-in is_struct is shown. > It is not easy to debug this kind of messages. My expectation is to see > not expanded macro in guards. >
Correct me if I'm wrong, but isn't this not just specific to custom guards? As far as I know, *all* macros behave this way because macro expansion happens at compile time, and this sort of runtime-error within the generated code *can't* know about the macro that produced it without some sort of new compiler artifact to track the source? -- 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 elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/e3b84348-39ae-4a45-95d5-ee0e8e6cf8a4%40googlegroups.com.
