You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes I need to nest macro directives, and when I do so, it's nice to indent them as one would do with code generally - just to keep it readable - however, erlfmt seems to want to remove all indentation, for example:
I don't think there's any mention of this in the style guide. As far as I can see, the macro-related stuff covers various topics, but doesn't consider flow control for macro definitions, and treats it as I would treat a list of several -defines or something. Also, I am not a frequent user of erlfmt, so maybe I am doing something wrong, making this a support request rather than a feature request.
I know nesting macro directives like this is probably Not Good™, but I'd prefer not to compound that by needing to have them flattened out.
Thanks!
The text was updated successfully, but these errors were encountered:
Yes, that's my experience too. My personal feeling, and what I saw in code, was that at one layer of nesting, there's no indentation, but beyond that there is:
Sometimes I need to nest macro directives, and when I do so, it's nice to indent them as one would do with code generally - just to keep it readable - however,
erlfmt
seems to want to remove all indentation, for example:--[apply erlfmt]-->
I don't think there's any mention of this in the style guide. As far as I can see, the macro-related stuff covers various topics, but doesn't consider flow control for macro definitions, and treats it as I would treat a list of several
-define
s or something. Also, I am not a frequent user oferlfmt
, so maybe I am doing something wrong, making this a support request rather than a feature request.I know nesting macro directives like this is probably Not Good™, but I'd prefer not to compound that by needing to have them flattened out.
Thanks!
The text was updated successfully, but these errors were encountered: