“Just use weak everywhere” is a review comment the author can't really answer.
Take a class instance that stores a callback, and the callback strongly captures that same instance. Two comments that give the author something to work with are “Could this capture be weak, with the callback doing nothing if the instance is already gone?” and “If this work has to finish after the original owner goes away, which object should keep it alive until then?”
The first proposes a non-owning edge and says what happens when the other end is missing. The second asks where ongoing ownership should live. They lead to different designs, and the actual requirement picks between them. Breaking the strong cycle is the easy part. Deciding how long each thing should live is the real question.
You can still disagree and reject the change outright. Swift's code of conduct asks for constructive criticism, and a precise comment is easier to defend or revise against. Name the relationship and the disagreement becomes something the author can answer.
