When running a large database in an environment challenged by limited hard-drive space, simple mode logging can be used to save space. If you then need to selectively purge a large number of rows using a delete query (not truncate), drive space has to be found for the unavoidable log growth that results from the delete. An obvious solution is to get some more drive space (either physically or in the cloud), detach the log and attach to a new log on the newly acquired drive space. A few minutes later, when the purge is complete, you can then repeat the detach and reattach process, moving the logging back to its original location and then get rid of the additional storage. Aside from the down time and the human effort, that is an acceptable solution.
My suggestion is that SQL Server be enhanced to eliminate both the down time and the human effort.