'I/O resource opened but safely closed' inspection

The closing part that goes in the finally block is a bit
ugly to look at:It's a nice candidate for a utility method, safeClose,
or something. Unfortunately, the inspection doesn't understand
that safeClose actually closes the resource. Would it be
possible to handle this case, or do I just accept things
as they stand?


1 comment
Comment actions Permalink

For now there's no real solution to this. There's already a tracker item for an extension, but no timeframe.

--Dave Griffith


Please sign in to leave a comment.