[randomtask]

It's possible for a library to return an error to indicate that a file is not found when you try and open a non-existent file. Then it's possible for a function that calls the open file function to decide whether that error should be translated into an exception i.e. should that file being missing break out of the current execution? There's no race condition there.

I don't think anyone reasonably expects a library to know the context of the file being opened and its importance in the logic of the rest of the program.