Closed
Description
Right now, if you want to get information about the behaviour_info/1
function that gets generated in behaviours, you have to do one of the following:
- Go to the docs for the
Behaviour
module. This is bad as that module is deprecated. - Google
behaviour_info elixir
, which returns sucky results (screenshot below) - Google
behaviour_info erlang
, where for me the third result is the Modules Erlang docs, where then I have to searchbehaviour_info
in the page.
This is all not ideal IMO, can we make it better? I’m a bit out of ideas. We could implement a mock Kernel.behaviour_info/1
function just to document stuff, but I’m not sure that's a good solution. Thoughts?
Metadata
Metadata
Assignees
Labels
No labels