Scop::init is used only during SCoP construction. Therefore ScopBuilder seems the more appropriate place for it. We integrate it onto its only caller ScopBuilder::buildScop where some other construction steps already took place.
There was a bail-out check
if (!scop->hasFeasibleRuntimeContext()) return;
at the end of the init function. Since hasFeasibleRuntimeContext has no side-effects, this was a no-op. Now it guards the call of verifyUses.
Follow-up patches could move the individual construction step methods to ScopBuilder as well.