if you have a better idea to make the macro not cause issues like that, i'm all ears. but if it's not guaranteed to be safe and not cause issues like this again, i'd like to see it removed.

Here, I think this should fix this the issue permanently: CB:40237

The bug happened once by now, but a non-functional change that basically only slightly shifts line numbers should never ever result in a build failure. this is why i'd say that the macro is buggy

Yeah I'm not saying it isn't, but let's just fix it rather than remove it immediately?

View Change

To view, visit change 40141. To unsubscribe, or for help writing mail filters, visit settings.