> This is come up from my discussion with Jason Alexon on Slack when he was trying to implement https://github.com/axelson/priv_check which checks for function calls to the private (aka marked as `@doc false`) functions.
My understanding is that you want to not warn on calls to private functions, as long as they are generated. If this is the case, the generated information is part of the metadata and the metadata is available in compilation tracers, which is what I would most likely use to trace all calls. > Such field could be a boolean, `mfa()` of the current macro, or even list of macro invocations. Any of these would be a helpful. I think the latter 2 options are most appealing, as it will allow for better control over the current context If you need this, then we'd need to expand :generated to store a module. A module most likely provides enough boundary, I can't see a function being ok to be called from SomeMod.a/1 but not SomeMod.b/1. -- 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/CAGnRm4JEkO3vkYCh%2Bimt%2B9op%2BjcXhaYZwEmBuJBL903TxEfOcQ%40mail.gmail.com.
