This is just an informal survey of HDF5 users regarding a request in changing default behavior of serial H5Fclose() to H5F_CLOSE_SEMI. As you may or may not know, by default H5Fclose() can return non-negative exit status (indicating success), yet still leave the file on disk actually open. This happens if the caller has (accidentally) left any objects in the file open. I would like to see this default behavior change and instead have H5Fclose() return negative exit status (indicating error), under these conditions. Either way, the file on disk is still left open. The difference is whether the caller gets any indication that something may have gone wrong with closing the file.
My understanding is that this could negatively impact libraries that use HDF5 as middleware (e.g. CGNS, netCDF, Silo, etc.) and where multiple different layers of software may have called H5Fopen() on the same file system path. Each call returns a unique hid_t HDF5 file handle and a later H5Fclose() by default, currently returns non-negative (success) because it has merely freed the associated hid_t resource and has not necessarily actually closed the file. However, I worry this use case is far less common than the one described above, where caller accidentally leaves open objects in the file but believes its been successfully closed because H5Fclose() returned non-negative (success) status.