Repository navigation
feature request: Add define to remove source_locations from each function #1111
Description
Activity
Interesting. I now wonder what is the performance overhead of the source locations...
The original PR doesn't show any performance degradation in automatic benchamarking: #835. Admittedly, those benchmarks don't really use throwing functions. I tried locally the benchmarks that do use those. The results aren't that significant either. So, as Vinnie said, measurements that show that such an option would result in improved performance are welcome.
Absent measurements it would be cool to see the generated object code. We could feature that in the Boost Diagnostics Suite literature, to show how it doesn't add measurable overhead (assuming that is the case)
Closing since OP wasn't responsive.
I dont see much reasons to have source location on each function as default arguments. Json is a hot path of many apps, performance is critical here, why there are source location on each .at without possibility to remove it?
I already have stacktrace from exception, i dont need source location