lol. this is so wrong.

I don’t disagree with you.
BUT — the problem is the existing project I was working on already had a ton of macros that were being used all over the code base (a huge code base). Refactoring the whole thing would have taken at least a week and would probably have caused regressions that would have been discovered only in production.
When working on new projects — we don’t use macros at all.
But in this post I gave an example on how to adopt Swift with old projects that do use macros (even if that is not the way you should be using macros).

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.