Dirty C++ Tricks from userver and Boost

I'll tell and show you how to create some great working C++ solutions "on the edge of tricks": getting stack trace from any exception without modifying third-party library code; replacing part of the exception mechanism on the fly to improve its performance; code with function execution at address 0x42 to do interesting things at compile-time; getting structure field names at compile-time without macros or code generation.

Please don't repeat this in production without consulting your colleagues!