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.
-
-
- Još 1 odgovor
Novi razgovor -
-
-
Should I use the C preprocessor on a Rust file?
- Još 1 odgovor
Novi razgovor -
-
-
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.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
You can always replace macros by copying and pasting code!

- Još 5 drugih odgovora
Novi razgovor -
-
-
disagree i guess, since i'll use it to cut down on boilerplate if it avoids enough of it
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
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.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.