Handling there is probably the right thing to do. I think the argument is that there is probably a better way of expressing that in code than exceptions. Perha

Handling there is probably the right thing to do. I think the argument is that there is probably a better way of expressing that in code than exceptions. Perhaps returning an Either<Data, ErrorCode> kind of value. There’s also an argument that that’s not truly an exception because it should be expected that an I/O error is a reasonable possibility. Things like OutOfMemory or VirtualMachineError are more what they may be thinking exceptions should be saved for. Truly unexpected things.