Get the latest tech news
Obscure feature + obscure feature + obscure feature = compiler bug
How piling on weird language features in our C++ SDK turned up a compiler bug.
But as a user of our SDK, one correct fix is “don’t use the same message for different assertions” - you shouldn’t be doing that anyway, because then you won’t get good diagnostic information back when something fails. Here it’s Optimization + Non-type Templates + Anonymous Namespaces; in another system it might be Leader Election + Network Fault + One Node Dies; in yet another it might be One Machine is Slower than Another + Clock Skew + Dropped Packet. Antithesis automatically creates different combinations of your operations and randomly applies faults while confirming that nothing goes wrong (that all your properties always hold).
Or read this on Hacker News