> starts to depend on the kind of resource to manage. Exactly, simple but not too simple. If the condition does not need to return early or can't, you don't.

> starts to depend on the kind of resource to manage. Exactly, simple but not too simple. If the condition does not need to return early or can't, you don't. > quickly end up managing file descriptors, sockets, handles, GUI resources In some of the cases you describe you wouldn't return early or depending on the need, but if you can you should to minimize work. Some examples: file descriptors you'd return early if the file does not exist, sockets you'd return if dropped or compromised and you have performed cleanup, handles if null, gui resources can be lots of things but if you were doing something where you needed to cleanup you can cleanup and return. In C# for instance you might wrap some of that in a using such as files, sockets, streams etc. Most of your examples you might already be in the meat of the return early flow and usually there is still a return at the very end but in/after the meat. Returning early isn't saying do a dirty break or asserting out, you don't return early before cleaning up if you are within some resource.