PRs welcome ! Only keep in mind the first sentence is a short summary. 
josevalim
Creator of Elixir
aiwaiwa
Before PRing though. What do you think? Imagine yourself a few months Elixir user!
use(module, opts \\ [])
Applies a module as a compile-time extension to the current context.
The use macro combines a require of the module with the invocation of its __using__/1 function, allowing the module to define macros, callbacks, or other compile-time constructs.
2
josevalim
Creator of Elixir
Maybe send a PR and link to it here so people can give feedback? I am not evading, I just think my opinion is the least important here.
4
aiwaiwa
LOL! You created one of the most readable and clear language syntax and you are not important!
2
hst337
code-shoily
… This is going to be very 
BartOtten
For those “eating code for breakfast”
Really like the new ‘default style’ directive for such information as the struggle was real sometimes.
1
hubertlepicki
The nutrition facts comparison is very good one, also because these can lie to you, like these one clearly don’t add up to 100:
This is going to be quite similar, but that’s not something that can be easily avoided.
What I would love to see, and maybe there is such thing already, is an information given to me back when I “use SomeModule” in my editor/IDE. I guess that’d be the language’s server doing, that would report to me, in a pop-up or some other form, what happened here, which behavior(s) was introduced, what functions were defined, what modules got imported, things like that.
The documentation is static, and has to be maintained, the language server is dynamic and can generate an actual report, that would take into consideration options pased to the “use” macro, to give me a precise overview of what actually happened to my code when I used it.
The same thing could be available for other macros, also “import” to know what functions got imported.
Again, this may already be available in full or partially, I’m not an expert on the subject.
EDIT: Oh hi there it’s me again commenting on a thread without reading it fully. Need to try this, not in language server and NeoVim specific but looks like what I suggested:
0
Qqwy
TypeCheck Core Team
Great idea!
@josevalim This is the first time I’ve seen the {: .info} syntax. I love how it looks, but starting at which version does ExDoc support this?
1
josevalim
Creator of Elixir
Honestly, we need both. Telling a newcomer that they can “see expanded macro” to figure what use does it not necessarily the best experience. We could introspect this automatically but it is hard to separate what is public (we set this attribute that directly impacts you or is public API) vs private (we generated this function/attribute that you should never care about). But the expanded macro feature is great for experienced devs.
Check ExDoc readme (we recently added tabsets too). In there since v0.28.x, more than a year ago.
4