Skip reference warnings to

[eksperimental]

No description provided.

[eksperimental]

There are two features that can be discussed, but are not intended to be covered by this PR:

1. Whether we want to support Mix tasks. ie. "mix foo", instead of using the Mix.Tasks.TASKNAME module.

2. Whether we want to skip references to a a module and everything inside (functions, types, etc). As of now, listing the Module would ignore the warning for that module in particular, but nothing else.

[josevalim]

Do you have any example of when we would use this feature?

[eksperimental]

@josevalim Sorry, it was in the commit log, but since it originally had two commits, it wasn't clear.

Closes #1192
Addresses #1151 (comment)

[eksperimental]

Basically when mentioning a hidden reference (i.e. with doc false), such as in #1151 (comment)

where calling ExUnit.Case.__using__/1, which is a macro with @doc false and it will emit a warning when referencing it.

This way we can mention a public reference that has no documentation and don't get a warning.

[josevalim]

@eksperimental oh, I see. I wonder if we can tackle this in some other way. Having to change a completely unrelated config file for a mistake happening in the documentation elsewhere is not very clear. Maybe we can use triple backticks to denote code sections with no syntax highlighting. We would need to change markdown first. For now, I will fix this in Elixir by referring to the function indirectly. Thank you!