To be fair, Iran had an enrichment program that they were actively hiding under a mountain, they were clearly developing for nuclear weapons, because if you have the enrichment capability why wouldn't you?
But on the other hand, I see that exactly as the reason we ought to be involved with Iran's nuclear program and actively supporting it.
Sure, but having nuclear reactors != having nuclear weapons. There are two ways to make nuclear weapons: enrichment and harvesting plutonium from reactors designed to make it.
Enrichment is almost certainly not going to be acceptable due to past and present conduct.
Harvesting is going to simply not be possible, because it requires a type of reactor designed for the task, and nearly all modern reactors are actively designed against it (known as proliferation resistant reactors). The US and allies won't sell LEU to the Sauds if they know they don't have proliferation resistant reactors.
Russia and Pakistan might though. Which is why it's important to lock the Sauds in on proliferation resistant reactors and LEU imports ASAP.
I assume that exploit is used in the sense of "takes advantage of" (eg. clang exploits signed overflow UB to omit this loop check)
It's useful to know which compilers are taking advantage of which UB, so when you're troubleshooting a bug that only occurs in one compiler and not another you can drill down and reason about which compiler uses which UB and perhaps more easily find the bug.
But on the other hand, I see that exactly as the reason we ought to be involved with Iran's nuclear program and actively supporting it.