Michał Muskała

The issue is not in defines, but in any usages of `?MACRO`. In particular, with no modifications to `-define` for the following example: ```erl -define(MUL(A, B), A * B). test()...

FWIW I think this will be largely limited by the current Erlang parser. erlfmt parser (which is used by erlang_ls right now) is significantly better for that and generally provides...

This is intentional. What erlfmt does in case like this is it reproduces the original source for the parts of the program it cannot handle correctly. Because Erlang macros are...

It's in here a bit lower: https://erlang.org/doc/man/yecc.html#more-examples I agree adding first-class support for yecc forms would be probably the "nicest" solution

> It can be done gradually. - There is the explicit "Erlang code." part of `.yrl` files - adding support for understanding and formatting it may be the first step....

Hey, sorry for taking so long to reply on this I think it would be better to do the reverse - to make sure, if possible, we always return the...

OTP 20 made dirty NIFs obligatory because it uses them internally, so I think it's perfectly fine to require them. Elixir itself will most probably require OTP 20 in the...

Some remarks: * `fiil_data` can be replaced by `:binary.copy` * one idea could be to precompute things like ones and zeros at compile-time and have them as literals. This could...

About the ones and zeros - you're right. I somehow overlooked the fact that we don't know the sizes 🤦‍♂️

I think there's a decision to be made about what formatting language should be used. As far as I can see we have 3 options: * strftime - which is...