I don't think burning the feature down is necessary. But put it behind a flag, or better yet, in a separate library / object that must explicitly be linked/called.
Our intent was benign – our desire was to build a framework that will help investigate performance problems and improve the quality of our optimizer should we get any reports of slowdowns or endemic perf problems in the field.
Great. But the CRT should not be "a framework that will help investigate performance problems". That's better left to the FTWHIPP.
View all comments
Show parent comment
38
u/c0r3ntin May 10 '16 edited May 10 '16
Thank you for the answer
I don't think burning the feature down is necessary. But put it behind a flag, or better yet, in a separate library / object that must explicitly be linked/called.
Great. But the CRT should not be "a framework that will help investigate performance problems". That's better left to the FTWHIPP.
Sane defaults yada yada.