User testimonial:

"I had this large crappy codebase that I couldn't make @safe. I tried putting $safe on main, it didn't work. Then I compiled it with DIP1028, and it built just fine, no change needed! Wow! Thanks, ShamWow!"

https://www.youtube.com/watch?v=LV6puTS14Ho

Walter: DIP 1028
Community: https://media.giphy.com/media/KbAMAJ0za8qNW/giphy.gif

On 5/27/20 9:08 AM, Andrei Alexandrescu wrote:
> User testimonial:
> 
> "I had this large crappy codebase that I couldn't make @safe. I tried putting $safe on main, it didn't work. Then I compiled it with DIP1028, and it built just fine, no change needed! Wow! Thanks, ShamWow!"
> 
> https://www.youtube.com/watch?v=LV6puTS14Ho

Johnny B. Noob from Nebraska, OK:

"I got tasked with increasing the safety of our codebase. I ran DIP1028 with great trepidation, having allocated a few days to examine the issues that it'll sure enough point out. We call some ungodly C routines, and I was expecting it would show me what code to vet manually. To my surprise, the code built flag-free. I had no idea we were safe all along. Thanks, ShamWow!"

On Wednesday, 27 May 2020 at 13:08:34 UTC, Andrei Alexandrescu wrote:
> User testimonial:
>
> "I had this large crappy codebase that I couldn't make @safe. I tried putting $safe on main, it didn't work. Then I compiled it with DIP1028, and it built just fine, no change needed! Wow! Thanks, ShamWow!"
>
> https://www.youtube.com/watch?v=LV6puTS14Ho

More seriously, when the user runs into unsafe extern code that was incorrectly marked as `@safe` or `@trusted`, do they say, "Hey, this library author pulled a ShamWow on me", or do they say, "Hey, these language designers pulled a ShamWow on me" ... ?