Should I use the C preprocessor on a Rust file?
-
-
-
you don’t already?
End of conversation
New conversation -
-
-
I feel that this 'anything else' should exclude code generation and copy&paste with more than, say, 30 lines of copied code. Also proc macros are a whole different kettle of fish.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You can always replace macros by copying and pasting code!

-
I chuckled, but no. In Servo for example we have macros that hide some values and provide only borrows to them, that’s not doable without them.
- 4 more replies
New conversation -
-
-
Almost agree. Strongly agree in terms of public API of libraries. But when it comes to writing tests, I pretty quickly reach for macros. But in my defense, they are usually pretty simple.
-
Sounds interesting. Could you link/name an example repo?
- 11 more replies
New conversation -
-
-
disagree i guess, since i'll use it to cut down on boilerplate if it avoids enough of it
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Macros can be a useful way to pair high performance code with a more readable in source representation that has less boiler plate, and isn't as much of a chore to read and write. Still, I understand macro hate is really common.
-
Basically I like inventing syntaxes that are a more useful and concise way to describe what I want to do, especially when I want to do that thing a lot.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.