Ruby `reject!`
I love this blog, but I&#x27;m not sure that I agree with this:<p>&gt; In my mind, I’d just rather not have a reject! at all, and callers who need to mutate an array in-place can figure out how to do safely with respect to their own use cases.<p>We ought to have a standard version of the reject! code precisely <i>because</i> it&#x27;s so difficult to get right. Saying application developers should solve the problem themselves just sounds like some sort of political move: &#x27;sure they may get the edge cases wrong, but then it will be their fault not ours&#x27;.<p>One of the best things about Ruby is that having helper methods for every kind of possible operation frees application developers from re-solving these edge-case problems and allows them to just write their business logic.