If your macro is generating AST like `ident"internal_storagecompact"` then change it to `bindSym"internal_storagecompact"`. `bindSym` by default uses "closed symbol scope" in contrast to "open symbol scope", as in the symbol is resolved when it's being generated in the macro rather than later. This will require `internal_storagecompact` to be declared before the macro though. [Documentation of bindSym](https://nim-lang.org/docs/macros.html#bindSym%2C%2CBindSymRule)
- Accessing private procs from macro in different module Pixeye
- Re: Accessing private procs from macro in different module Hlaaftana
