I’ve just come across a library that had import Foo.BinaryUtils, warn: false peppered through it. That looked like a code smell so I started investigating. It turned out this module had macros in it used for bitstring specifiers, e.g.: defmacro uint do quote do: little - unsigned - 16 end …

Turns out I was misunderstanding how require and import work. What this library should have been doing is import Foo.BinaryUtils, only: :macros, which communicates much more clearly the intent.

[image] IslandUsurper: import Foo.BinaryUtils, warn: false Elixir will not complain if you don’t not use all the macros from an imported module. It may be complaining because you are not using any at all. Feel free to share some code, either gist or a repo and I can have a look at it and giv…

It’s definitely using the macros. Taking out the import prevents compilation, and the error shows where the macro is used. And I just found out that the warning still happens if I replace warn: false with only: :macros. The repo is Scrub , but I didn’t write it.

[image] IslandUsurper: The repo is Scrub , but I didn’t write it. Where is the specific line of code I should look at?

Lots of examples, but lib/scrub/session/protocol.ex:28 and following is a good one to look at.

Gah, never mind. It’s the lib/scrub.ex where the warning happens, but that module doesn’t actually use the macros. Everything works as intended.

Bitstring specifier macros

Questions & Help Questions

eksperimental December 14, 2021, 8:01pm 5

Where is the specific line of code I should look at?