Macro file compilation fails with unknown identifier

[datwaft]

Hello!

I am trying to make a proof of concept with tangerine but found a block when migrating my macros from hotpot to tangerine.

As you can see in the following screenshot the compilation fails when trying to compile my macro module.

The error is the following:

:: COMPILE ERROR
  xxx conf/macro/pack.fnl
      Compile error in conf/macro/pack.fnl:21
        unknown identifier in strict mode: assert-compile

I have the code in a Github repository that you can see here. The repository can be executed using Docker for if you want to personally test it.

[udayvir-singh]

Macros have to be suffixed with "macros.fnl" to prevent them from being compiled.

For example:

init-macros.fnl
pack-macros.fnl
example-macros.fnl

So just rename conf/macro/pack.fnl to conf/macro/pack-macros.fnl.

[udayvir-singh]

see pull request datwaft/tangerine-proof-of-concept#1

[datwaft]

I see. Thanks for your help!

Is there any way that in the future they could be detected by the folder name macros/macro too?

I think it's too verbose to add -macros to every macro file.

[udayvir-singh]

@datwaft

all lot of people mix macros/normal fennel files together,
so it is impossible to be sure at compile time that a folder only contains macros.

take this folder for example:

macros
├── utils
│  └── helpers.fnl
├── neovim.fnl
└── packer.fnl

this is more easy to deal with:

macros
├── utils
│  └── helpers.fnl
├── neovim-macros.fnl
└── packer-macros.fnl

[datwaft]

Understood! Thanks for your help!

I am used to hotpot knowing whether a module is a macro module based on how it's required, so I was expecting to be able to do the same with tangerine.

Thanks once again for your help!

[shaunsingh]

Could you kindly create an option to toggle compiling all files under macro/ folders as well? I prefer keeping all my macros in a folder and adding -macros to the end of each file is a bit excessive.