-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Macro.to_string/1
instead of parsing specs by "hand"
#34
Conversation
[]
[]
, integer, range and bitstrings
[]
, integer, range and bitstrings[]
, integer, range, bitstrings, nested types and guards
[]
, integer, range, bitstrings, nested types and guards[]
, integer, range, bitstrings and nested types
[]
, integer, range, bitstrings and nested typesMacro.to_string/1
instead of parsing specs by "hand"
lib/contexted/module_analyzer.ex
Outdated
defp format_type({:type, _, type_name, _}, _module), do: "#{type_name}()" | ||
@spec build_spec(tuple()) :: String.t() | ||
defp build_spec({{function_name, _arity}, spec}) do | ||
first_spec = hd(spec) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it mean there can be more of these? Meaning, does spec
hold multiple definitions of specs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does hold multiple specs for one function. I have added support for multiple specs.
No description provided.