(since 3.0.0)
Avoid -spec
attributes.
This rule is meant to be used in header files only.
Defining specs in public header files (especially those intended for inclusion via -include_lib(...)
)
might lead to spec clashes between projects and even a single big project's modules.
Instead, specs should be defined next to the functions they're specifying.
Works on
.beam
file? Yes, but it's not useful there. This rule is meant to be used for header files.
- None.
{elvis_style, no_specs}